پولیگون

The easiest way to get started with bor is to install the packages using the command below. Please take a look at the releases section to find the latest stable version of bor. The network accepts mainnet , or amoy and the node type accepts validator or sentry or archive . The installation script does the following things: Create a new user named bor . Install the bor binary at /usr/bin/bor . Dump the suitable config file (based on the network and node type provided) at /var/lib/bor and use it as the home dir. Create a systemd service named bor at /lib/systemd/system/bor.service which starts bor using the config file as bor user. The releases supports both the networks i.e. Polygon Mainnet, and Amoy (Testnet) unless explicitly specified. Before the stable release for mainnet, pre-releases will be available marked with beta tag for deploying on Amoy (testnet). On sufficient testing, stable release for mainnet will be announced with a forum post. Building from source Install Go (version 1.19 or later) and a C compiler. Clone the repository and build the binary using the following commands: Start bor using the ideal config files for the validator and sentry provided in the packaging folder. To build full set of utilities, run: Run unit and integration tests Post v0.3.0 release, bor uses a new command line interface (cli). The new-cli (located at internal/cli ) has been built while keeping the flag usage similar to old-cli (located at cmd/geth ) with a few notable changes. Please refer to docs section for the flag usage guide and example. Bor includes a Parity-compatible trace namespace ( trace block , trace transaction , trace replayTransaction , trace replayBlockTransactions , trace call , trace callMany ). These methods are disabled by default because they are expensive and require an archive node. Enable with the --rpc.enabletrace flag (or enabletrace = true under [jsonrpc] in TOML): Requirements: Archive node ( --gcmode archive ) Sufficient HTTP write timeout for deep blocks if needed — the trace methods themselves already use a 60s per-phase budget, while the HTTP response write timeout defaults to 30s. It is configurable via TOML only: Known limitations vs Polygon Erigon: trace call / trace callMany still require the simulated sender to pass Bor's upfront gas balance check; once funded, gas debit/refund is suppressed. trace block omits the state-sync pseudo-transaction for pre-Madhugiri blocks (< 80,084,800 on mainnet); post-Madhugiri blocks are fully supported. vmTrace for a post-Madhugiri state-sync transaction reports an empty ops list (state-sync events execute outside the regular EVM opcode flow). Documentation The official documentation for the Polygon PoS chain can be found here. It contains all the conceptual and architectural details of the chain along with an operational guide for users running the nodes. New release announcements and discussions can be found on our forum page. Polygon improvement proposals can be found here Thank you for considering helping out with the source code! We welcome contributions from anyone on the internet, and are grateful for even the smallest of fixes! If you'd like to contribute to bor, please fork, fix, commit, and send a pull request for the maintainers to review and merge into the main code base. The Bor library (i.e. all code outside of the cmd directory) is licensed under the GNU Lesser General Public License v3.0, also included in our repository in the COPYING.LESSER file. The Bor binaries (i.e. all code inside of the cmd directory) are licensed under the GNU General Public License v3.0, also included in our repository in the COPYING file.