* fix(vote-account): rangeError [ERR_OUT_OF_RANGE] error
The web3 buffer layout is out-of-date with the current `VoteState` implementation. The buffer layout
is updated to match the structure in
https://github.com/solana-labs/solana/blob/master/account-decoder/src/parse_vote.rsfix#20786
* docs(vote account): update reference to match new payload
* fix(vote-account): update buffer layout for prior voters
Update buffer layout for prior voters to match serialized data
* fix(vote-account): response showing buffers instead of public keys
transform buffers into public keys
* refactor(vote account): extract parsing into function calls
* feat(vote account): address PR comments
* fix(web3.js vote account): start prior voters array from given index
* fix(web3.js vote account): incorrect data for prior voters array
* Update web3.js/src/vote-account.ts
Co-authored-by: Justin Starry <justin.m.starry@gmail.com>
Co-authored-by: Justin Starry <justin.m.starry@gmail.com>
Added Vivaldi to the list of browsers with support for Phantom. I've been using this browser for Phantom and have installed it on a few dozen customer's Chromium based Vivaldi browsers, on both Windows and various Linux distros over the past few months with flawless, error free operation.
# Problem
The initial proposal ruled out implementing BigTable queries for
the `getBlockTime` RPC, but then it was implemented a couple months
later. Indicating that the functionality was never implemented in
the "implemented-proposals" document is a little confusing, so let's
bring the document in line with what actually happened. 🦾
# Summary of Changes
Remove the blurb about how `getBlockTime` was going to be deprecated
and add it to the list of calls that didn't yet support BigTable
queries at the time the proposal was written.
Allow u16::MAX to be specified for the instruction index. This makes it
possible to specify the current instruction, so it is not necessary to
know the instruction number.
Summary of Changes
Create a plugin mechanism in the accounts update path so that accounts data can be streamed out to external data stores (be it Kafka or Postgres). The plugin mechanism allows
Data stores of connection strings/credentials to be configured,
Accounts with patterns to be streamed
PostgreSQL implementation of the streaming for different destination stores to be plugged in.
The code comprises 4 major parts:
accountsdb-plugin-intf: defines the plugin interface which concrete plugin should implement.
accountsdb-plugin-manager: manages the load/unload of plugins and provide interfaces which the validator can notify of accounts update to plugins.
accountsdb-plugin-postgres: the concrete plugin implementation for PostgreSQL
The validator integrations: updated streamed right after snapshot restore and after account update from transaction processing or other real updates.
The plugin is optionally loaded on demand by new validator CLI argument -- there is no impact if the plugin is not loaded.
Justin Starry
Boris Vujicic
Melroy van den Berg
Tyera Eulberg
Alexander Meißner
Brian Anderson
Trent Nelson
Michael Vines
Colin Ogoo
CrazySerGo
Aiham
Ben Newhouse
Arthur Burkart
Ikko Ashimine
Jeff Biseda
Jon Cinque
Bradley D. Thornton
yihau
Jack May
Slavomir
Elliot Lee
Ted Robertson
Sean Young
sgmoore
Lijun Wang