mirror of
https://gitlab.com/pulsechaincom/erigon-pulse.git
synced 2024-12-31 16:21:21 +00:00
42e8db3958
Blob transactions are SSZ encoded, so it had to be added to decoding. There are 2 encoding forms: `network` and `minimal` (usual). Network encoded blob transactions include "wrapper data" which are `kzgs`, `blobs` and `proofs`, and decoded by `DecodeWrappedTransaction`. For previous types of transactions the network encoding is no different. Execution-payloads / blocks use the minimal encoding of transactions. In the transaction-pool and local transaction-journal the network encoding is used. Concerns: 1. Possible performance reduction caused by these changes, not sure if streams are better then slices. Go slices in this modifications are read-only, so they should be referred to the same underlying array and passed by a reference. 2. If `DecodeWrappedTransaction` and `DecodeTransaction` will create confusion and should be merged into one function. |
||
|---|---|---|
| .. | ||
| adapter | ||
| app | ||
| backup | ||
| builder | ||
| cli | ||
| cmdtest | ||
| debug | ||
| engineapi | ||
| logging | ||
| mock | ||
| node | ||
| rlphacks | ||
| rpchelper | ||
| services | ||
| shards | ||
| snapshotsync | ||
| stages | ||
| testlog | ||
| transactions | ||
| trie | ||
| README.md | ||
Erigon-API
Erigon-API is a set of tools for building applications containing Erigon node.
Our own binary erigon is built using it.
Modules
-
cli- erigon-cli, methods & helpers to run a CLI app with Erigon node. -
node- represents an Ethereum node, running devp2p and sync and writing state to the database. -
stagedsync- staged sync algorithm.
Examples
-
erigon- our binary is using erigon-api with all defaults -
erigoncustom- a very simple example of adding a custom stage, a custom bucket and a custom command-line parameter -
erigon-examples - a series of examples for Erigon api