I wanted to use this sysvar to get a recent block hash, but I didn't
know whether the first or the last entry contains the most recent block
hash.
By calling it for mainnet, printing the results, and comparing that to
the recent blocks on solanabeach.io/blocks, I discovered that the
entries are ordered from most recent to least recent. Document this to
save future readers the trouble.
(cherry picked from commit 94ab0eb49f
)
Co-authored-by: Ruud van Asseldonk <ruud@chorus.one>
Docs Readme
Solana's Docs are built using Docusaurus 2 with npm
.
Static content delivery is handled using vercel
.
Installing Docusaurus
$ npm install
Local Development
This command starts a local development server and open up a browser window. Most changes are reflected live without having to restart the server. (You might have to run build.sh first if you run into failures)
$ npm run start
Build Locally
This command generates static content into the build
directory and can be
served using any static contents hosting service.
$ docs/build.sh
CI Build Flow
The docs are built and published in Travis CI with the docs/build.sh
script.
On each PR, the docs are built, but not published.
In each post-commit build, docs are built and published using vercel
to their
respective domain depending on the build branch.
- Master branch docs are published to
edge.docs.solana.com
- Beta branch docs are published to
beta.docs.solana.com
- Latest release tag docs are published to
docs.solana.com