README
¶
Syncer
The Syncer package provides support for syncing blocks from any Rosetta Node API implementation. If you want to see an example of how to use this package, take a look at rosetta-cli.
Features
- Automatic handling of block re-orgs
- Multi-threaded block fetching (using the
fetcherpackage) - Implementable
Handlerto define your own block processing logic (ex: store processed blocks to a db or print our balance changes)
Installation
go get github.com/coinbase/rosetta-sdk-go/syncer
Future Work
- Sync multiple shards in a sharded blockchain
Documentation
¶
Index ¶
Constants ¶
const ( // PastBlockSize is the maximum number of previously // processed blocks we keep in the syncer to handle // reorgs correctly. If there is a reorg greater than // PastBlockSize, it will not be handled correctly. // // TODO: make configurable PastBlockSize = 20 )
Variables ¶
This section is empty.
Functions ¶
This section is empty.
Types ¶
type Handler ¶
type Handler interface {
BlockAdded(
ctx context.Context,
block *types.Block,
) error
BlockRemoved(
ctx context.Context,
block *types.BlockIdentifier,
) error
}
Handler is called at various times during the sync cycle to handle different events. It is common to write logs or perform reconciliation in the sync processor.
type Syncer ¶
type Syncer struct {
// contains filtered or unexported fields
}
Syncer coordinates blockchain syncing without relying on a storage interface. Instead, it calls a provided Handler whenever a block is added or removed. This provides the client the opportunity to define the logic used to handle each new block. In the rosetta-cli, we handle reconciliation, state storage, and logging in the handler.
func New ¶
func New( network *types.NetworkIdentifier, fetcher *fetcher.Fetcher, handler Handler, cancel context.CancelFunc, pastBlocks []*types.BlockIdentifier, ) *Syncer
New creates a new Syncer. If pastBlocks is left nil, it will be set to an empty slice.
Source Files