GitHub Explorer

by Alexey Ratnikov

GitHub Explorer|TRENDING COMPARE|FEEDBACK

Search Results

Found 69 repositories(showing 30)

nate.283090

Nate0634034090

🧡60

LGPL-2.1

Updated 3 weeks ago

Liberty-House-Club-Whitepaper

Mdshobu

🧡60

# Liberty House Club **A Parallel Binance Chain to Enable Smart Contracts** _NOTE: This document is under development. Please check regularly for updates!_ ## Table of Contents - [Motivation](#motivation) - [Design Principles](#design-principles) - [Consensus and Validator Quorum](#consensus-and-validator-quorum) * [Proof of Staked Authority](#proof-of-staked-authority) * [Validator Quorum](#validator-quorum) * [Security and Finality](#security-and-finality) * [Reward](#reward) - [Token Economy](#token-economy) * [Native Token](#native-token) * [Other Tokens](#other-tokens) - [Cross-Chain Transfer and Communication](#cross-chain-transfer-and-communication) * [Cross-Chain Transfer](#cross-chain-transfer) * [BC to BSC Architecture](#bc-to-bsc-architecture) * [BSC to BC Architecture](#bsc-to-bc-architecture) * [Timeout and Error Handling](#timeout-and-error-handling) * [Cross-Chain User Experience](#cross-chain-user-experience) * [Cross-Chain Contract Event](#cross-chain-contract-event) - [Staking and Governance](#staking-and-governance) * [Staking on BC](#staking-on-bc) * [Rewarding](#rewarding) * [Slashing](#slashing) - [Relayers](#relayers) * [BSC Relayers](#bsc-relayers) * [Oracle Relayers](#oracle-relayers) - [Outlook](#outlook) # Motivation After its mainnet community [launch](https://www.binance.com/en/blog/327334696200323072/Binance-DEX-Launches-on-Binance-Chain-Invites-Further-Community-Development) in April 2019, [Binance Chain](https://www.binance.org) has exhibited its high speed and large throughput design. Binance Chain’s primary focus, its native [decentralized application](https://en.wikipedia.org/wiki/Decentralized_application) (“dApp”) [Binance DEX](https://www.binance.org/trade), has demonstrated its low-latency matching with large capacity headroom by handling millions of trading volume in a short time. Flexibility and usability are often in an inverse relationship with performance. The concentration on providing a convenient digital asset issuing and trading venue also brings limitations. Binance Chain's most requested feature is the programmable extendibility, or simply the [Smart Contract](https://en.wikipedia.org/wiki/Smart_contract) and Virtual Machine functions. Digital asset issuers and owners struggle to add new decentralized features for their assets or introduce any sort of community governance and activities. Despite this high demand for adding the Smart Contract feature onto Binance Chain, it is a hard decision to make. The execution of a Smart Contract may slow down the exchange function and add non-deterministic factors to trading. If that compromise could be tolerated, it might be a straightforward idea to introduce a new Virtual Machine specification based on [Tendermint](https://tendermint.com/core/), based on the current underlying consensus protocol and major [RPC](https://docs.binance.org/api-reference/node-rpc.html) implementation of Binance Chain. But all these will increase the learning requirements for all existing dApp communities, and will not be very welcomed. We propose a parallel blockchain of the current Binance Chain to retain the high performance of the native DEX blockchain and to support a friendly Smart Contract function at the same time. # Design Principles After the creation of the parallel blockchain into the Binance Chain ecosystem, two blockchains will run side by side to provide different services. The new parallel chain will be called “**Binance Smart Chain**” (short as “**BSC**” for the below sections), while the existing mainnet remains named “**Binance Chain**” (short as “**BC**” for the below sections). Here are the design principles of **BSC**: 1. **Standalone Blockchain**: technically, BSC is a standalone blockchain, instead of a layer-2 solution. Most BSC fundamental technical and business functions should be self-contained so that it can run well even if the BC stopped for a short period. 2. **Ethereum Compatibility**: The first practical and widely-used Smart Contract platform is Ethereum. To take advantage of the relatively mature applications and community, BSC chooses to be compatible with the existing Ethereum mainnet. This means most of the **dApps**, ecosystem components, and toolings will work with BSC and require zero or minimum changes; BSC node will require similar (or a bit higher) hardware specification and skills to run and operate. The implementation should leave room for BSC to catch up with further Ethereum upgrades. 3. **Staking Involved Consensus and Governance**: Staking-based consensus is more environmentally friendly and leaves more flexible option to the community governance. Expectedly, this consensus should enable better network performance over [proof-of-work](https://en.wikipedia.org/wiki/Proof_of_work) blockchain system, i.e., faster blocking time and higher transaction capacity. 4. **Native Cross-Chain Communication**: both BC and BSC will be implemented with native support for cross-chain communication among the two blockchains. The communication protocol should be bi-directional, decentralized, and trustless. It will concentrate on moving digital assets between BC and BSC, i.e., [BEP2](https://github.com/binance-chain/BEPs/blob/master/BEP2.md) tokens, and eventually, other BEP tokens introduced later. The protocol should care for the minimum of other items stored in the state of the blockchains, with only a few exceptions. # Consensus and Validator Quorum Based on the above design principles, the consensus protocol of BSC is to fulfill the following goals: 1. Blocking time should be shorter than Ethereum network, e.g. 5 seconds or even shorter. 2. It requires limited time to confirm the finality of transactions, e.g. around 1-min level or shorter. 3. There is no inflation of native token: BNB, the block reward is collected from transaction fees, and it will be paid in BNB. 4. It is compatible with Ethereum system as much as possible. 5. It allows modern [proof-of-stake](https://en.wikipedia.org/wiki/Proof_of_stake) blockchain network governance. ## Proof of Staked Authority Although Proof-of-Work (PoW) has been recognized as a practical mechanism to implement a decentralized network, it is not friendly to the environment and also requires a large size of participants to maintain the security. Ethereum and some other blockchain networks, such as [MATIC Bor](https://github.com/maticnetwork/bor), [TOMOChain](https://tomochain.com/), [GoChain](https://gochain.io/), [xDAI](https://xdai.io/), do use [Proof-of-Authority(PoA)](https://en.wikipedia.org/wiki/Proof_of_authority) or its variants in different scenarios, including both testnet and mainnet. PoA provides some defense to 51% attack, with improved efficiency and tolerance to certain levels of Byzantine players (malicious or hacked). It serves as an easy choice to pick as the fundamentals. Meanwhile, the PoA protocol is most criticized for being not as decentralized as PoW, as the validators, i.e. the nodes that take turns to produce blocks, have all the authorities and are prone to corruption and security attacks. Other blockchains, such as EOS and Lisk both, introduce different types of [Delegated Proof of Stake (DPoS)](https://en.bitcoinwiki.org/wiki/DPoS) to allow the token holders to vote and elect the validator set. It increases the decentralization and favors community governance. BSC here proposes to combine DPoS and PoA for consensus, so that: 1. Blocks are produced by a limited set of validators 2. Validators take turns to produce blocks in a PoA manner, similar to [Ethereum’s Clique](https://eips.ethereum.org/EIPS/eip-225) consensus design 3. Validator set are elected in and out based on a staking based governance ## Validator Quorum In the genesis stage, a few trusted nodes will run as the initial Validator Set. After the blocking starts, anyone can compete to join as candidates to elect as a validator. The staking status decides the top 21 most staked nodes to be the next validator set, and such an election will repeat every 24 hours. **BNB** is the token used to stake for BSC. In order to remain as compatible as Ethereum and upgradeable to future consensus protocols to be developed, BSC chooses to rely on the **BC** for staking management (Please refer to the below “[Staking and Governance](#staking-and-governance)” section). There is a **dedicated staking module for BSC on BC**. It will accept BSC staking from BNB holders and calculate the highest staked node set. Upon every UTC midnight, BC will issue a verifiable `ValidatorSetUpdate` cross-chain message to notify BSC to update its validator set. While producing further blocks, the existing BSC validators check whether there is a `ValidatorSetUpdate` message relayed onto BSC periodically. If there is, they will update the validator set after an **epoch period**, i.e. a predefined number of blocking time. For example, if BSC produces a block every 5 seconds, and the epoch period is 240 blocks, then the current validator set will check and update the validator set for the next epoch in 1200 seconds (20 minutes). ## Security and Finality Given there are more than ½\*N+1 validators are honest, PoA based networks usually work securely and properly. However, there are still cases where certain amount Byzantine validators may still manage to attack the network, e.g. through the “[Clone Attack](https://arxiv.org/pdf/1902.10244.pdf)”. To secure as much as BC, BSC users are encouraged to wait until receiving blocks sealed by more than ⅔\*N+1 different validators. In that way, the BSC can be trusted at a similar security level to BC and can tolerate less than ⅓\*N Byzantine validators. With 21 validators, if the block time is 5 seconds, the ⅔\*N+1 different validator seals will need a time period of (⅔\*21+1)*5 = 75 seconds. Any critical applications for BSC may have to wait for ⅔\*N+1 to ensure a relatively secure finality. However, besides such arrangement, BSC does introduce **Slashing** logic to penalize Byzantine validators for **double signing** or **inavailability**, which will be covered in the “Staking and Governance” section later. This Slashing logic will expose the malicious validators in a very short time and make the “Clone Attack” very hard or extremely non-beneficial to execute. With this enhancement, ½\*N+1 or even fewer blocks are enough as confirmation for most transactions. ## Reward All the BSC validators in the current validator set will be rewarded with transaction **fees in BNB**. As BNB is not an inflationary token, there will be no mining rewards as what Bitcoin and Ethereum network generate, and the gas fee is the major reward for validators. As BNB is also utility tokens with other use cases, delegators and validators will still enjoy other benefits of holding BNB. The reward for validators is the fees collected from transactions in each block. Validators can decide how much to give back to the delegators who stake their BNB to them, in order to attract more staking. Every validator will take turns to produce the blocks in the same probability (if they stick to 100% liveness), thus, in the long run, all the stable validators may get a similar size of the reward. Meanwhile, the stakes on each validator may be different, so this brings a counter-intuitive situation that more users trust and delegate to one validator, they potentially get less reward. So rational delegators will tend to delegate to the one with fewer stakes as long as the validator is still trustful (insecure validator may bring slashable risk). In the end, the stakes on all the validators will have less variation. This will actually prevent the stake concentration and “winner wins forever” problem seen on some other networks. Some parts of the gas fee will also be rewarded to relayers for Cross-Chain communication. Please refer to the “[Relayers](#relayers)” section below. # Token Economy BC and BSC share the same token universe for BNB and BEP2 tokens. This defines: 1. The same token can circulate on both networks, and flow between them bi-directionally via a cross-chain communication mechanism. 2. The total circulation of the same token should be managed across the two networks, i.e. the total effective supply of a token should be the sum of the token’s total effective supply on both BSC and BC. 3. The tokens can be initially created on BSC in a similar format as ERC20 token standard, or on BC as a BEP2, then created on the other. There are native ways on both networks to link the two and secure the total supply of the token. ## Native Token BNB will run on BSC in the same way as ETH runs on Ethereum so that it remains as “native token” for both BSC and BC. This means, in addition to BNB is used to pay most of the fees on Binance Chain and Binance DEX, BNB will be also used to: 1. pay “fees“ to deploy smart contracts on BSC 2. stake on selected BSC validators, and get corresponding rewards 3. perform cross-chain operations, such as transfer token assets across BC and BSC ### Seed Fund Certain amounts of BNB will be burnt on BC and minted on BSC during its genesis stage. This amount is called “Seed Fund” to circulate on BSC after the first block, which will be dispatched to the initial BC-to-BSC Relayer(described in later sections) and initial validator set introduced at genesis. These BNBs are used to pay transaction fees in the early stage to transfer more BNB from BC onto BSC via the cross-chain mechanism. The BNB cross-chain transfer is discussed in a later section, but for BC to BSC transfer, it is generally to lock BNB on BC from the source address of the transfer to a system-controlled address and unlock the corresponding amount from special contract to the target address of the transfer on BSC, or reversely, when transferring from BSC to BC, it is to lock BNB from the source address on BSC into a special contract and release locked amount on BC from the system address to the target address. The logic is related to native code on BC and a series of smart contracts on BSC. ## Other Tokens BC supports BEP2 tokens and upcoming [BEP8 tokens](https://github.com/binance-chain/BEPs/pull/69), which are native assets transferrable and tradable (if listed) via fast transactions and sub-second finality. Meanwhile, as BSC is Ethereum compatible, it is natural to support ERC20 tokens on BSC, which here is called “**BEP2E**” (with the real name to be introduced by the future BEPs,it potentially covers BEP8 as well). BEP2E may be “Enhanced” by adding a few more methods to expose more information, such as token denomination, decimal precision definition and the owner address who can decide the Token Binding across the chains. BSC and BC work together to ensure that one token can circulate in both formats with confirmed total supply and be used in different use cases. ### Token Binding BEP2 tokens will be extended to host a new attribute to associate the token with a BSC BEP2E token contract, called “**Binder**”, and this process of association is called “**Token Binding**”. Token Binding can happen at any time after BEP2 and BEP2E are ready. The token owners of either BEP2 or BEP2E don’t need to bother about the Binding, until before they really want to use the tokens on different scenarios. Issuers can either create BEP2 first or BEP2E first, and they can be bound at a later time. Of course, it is encouraged for all the issuers of BEP2 and BEP2E to set the Binding up early after the issuance. A typical procedure to bind the BEP2 and BEP2E will be like the below: 1. Ensure both the BEP2 token and the BEP2E token both exist on each blockchain, with the same total supply. BEP2E should have 3 more methods than typical ERC20 token standard: * symbol(): get token symbol * decimals(): get the number of the token decimal digits * owner(): get **BEP2E contract owner’s address.** This value should be initialized in the BEP2E contract constructor so that the further binding action can verify whether the action is from the BEP2E owner. 2. Decide the initial circulation on both blockchains. Suppose the total supply is *S*, and the expected initial circulating supply on BC is *K*, then the owner should lock S-K tokens to a system controlled address on BC. 3. Equivalently, *K* tokens is locked in the special contract on BSC, which handles major binding functions and is named as **TokenHub**. The issuer of the BEP2E token should lock the *K* amount of that token into TokenHub, resulting in *S-K* tokens to circulate on BSC. Thus the total circulation across 2 blockchains remains as *S*. 4. The issuer of BEP2 token sends the bind transaction on BC. Once the transaction is executed successfully after proper verification: * It transfers *S-K* tokens to a system-controlled address on BC. * A cross-chain bind request package will be created, waiting for Relayers to relay. 5. BSC Relayers will relay the cross-chain bind request package into **TokenHub** on BSC, and the corresponding request and information will be stored into the contract. 6. The contract owner and only the owner can run a special method of TokenHub contract, `ApproveBind`, to verify the binding request to mark it as a success. It will confirm: * the token has not been bound; * the binding is for the proper symbol, with proper total supply and decimal information; * the proper lock are done on both networks; 10. Once the `ApproveBind` method has succeeded, TokenHub will mark the two tokens are bounded and share the same circulation on BSC, and the status will be propagated back to BC. After this final confirmation, the BEP2E contract address and decimals will be written onto the BEP2 token as a new attribute on BC, and the tokens can be transferred across the two blockchains bidirectionally. If the ApproveBind fails, the failure event will also be propagated back to BC to release the locked tokens, and the above steps can be re-tried later. # Cross-Chain Transfer and Communication Cross-chain communication is the key foundation to allow the community to take advantage of the dual chain structure: * users are free to create any tokenization, financial products, and digital assets on BSC or BC as they wish * the items on BSC can be manually and programmingly traded and circulated in a stable, high throughput, lighting fast and friendly environment of BC * users can operate these in one UI and tooling ecosystem. ## Cross-Chain Transfer The cross-chain transfer is the key communication between the two blockchains. Essentially the logic is: 1. the `transfer-out` blockchain will lock the amount from source owner addresses into a system controlled address/contracts; 2. the `transfer-in` blockchain will unlock the amount from the system controlled address/contracts and send it to target addresses. The cross-chain transfer package message should allow the BSC Relayers and BC **Oracle Relayers** to verify: 1. Enough amount of token assets are removed from the source address and locked into a system controlled addresses/contracts on the source blockchain. And this can be confirmed on the target blockchain. 2. Proper amounts of token assets are released from a system controlled addresses/contracts and allocated into target addresses on the target blockchain. If this fails, it can be confirmed on source blockchain, so that the locked token can be released back (may deduct fees). 3. The sum of the total circulation of the token assets across the 2 blockchains are not changed after this transfer action completes, no matter if the transfer succeeds or not. ![cross-chain](./assets/cross-chain.png) The architecture of cross-chain communication is as in the above diagram. To accommodate the 2 heteroid systems, communication handling is different in each direction. ## BC to BSC Architecture BC is a Tendermint-based, instant finality blockchain. Validators with at least ⅔\*N+1 of the total voting power will co-sign each block on the chain. So that it is practical to verify the block transactions and even the state value via **Block Header** and **Merkle Proof** verification. This has been researched and implemented as “**Light-Client Protocol**”, which are intensively discussed in [the Ethereum](https://github.com/ethereum/wiki/wiki/Light-client-protocol) community, studied and implemented for [Cosmos inter-chain communication](https://github.com/cosmos/ics/blob/a4173c91560567bdb7cc9abee8e61256fc3725e9/spec/ics-007-tendermint-client/README.md). BC-to-BSC communication will be verified in an “**on-chain light client**” implemented via BSC **Smart Contracts** (some of them may be **“pre-compiled”**). After some transactions and state change happen on BC, if a transaction is defined to trigger cross-chain communication,the Cross-chain “**package**” message will be created and **BSC Relayers** will pass and submit them onto BSC as data into the "build-in system contracts". The build-in system contracts will verify the package and execute the transactions if it passes the verification. The verification will be guaranteed with the below design: 1. BC blocking status will be synced to the light client contracts on BSC from time to time, via block header and pre-commits, for the below information: * block and app hash of BC that are signed by validators * current validatorset, and validator set update 2. the key-value from the blockchain state will be verified based on the Merkle Proof and information from above #1. After confirming the key-value is accurate and trustful, the build-in system contracts will execute the actions corresponding to the cross-chain packages. Some examples of such packages that can be created for BC-to-BSC are: 1. Bind: bind the BEP2 tokens and BEP2E 2. Transfer: transfer tokens after binding, this means the circulation will decrease (be locked) from BC and appear in the target address balance on BSC 3. Error Handling: to handle any timeout/failure event for BSC-to-BC communication 4. Validatorset update of BSC To ensure no duplication, proper message sequence and timely timeout, there is a “Channel” concept introduced on BC to manage any types of the communication. For relayers, please also refer to the below “Relayers” section. ## BSC to BC Architecture BSC uses Proof of Staked Authority consensus protocol, which has a chance to fork and requires confirmation of more blocks. One block only has the signature of one validator, so that it is not easy to rely on one block to verify data from BSC. To take full advantage of validator quorum of BC, an idea similar to many [Bridge ](https://github.com/poanetwork/poa-bridge)or Oracle blockchains is adopted: 1. The cross-chain communication requests from BSC will be submitted and executed onto BSC as transactions. The execution of the transanction wil emit `Events`, and such events can be observed and packaged in certain “**Oracle**” onto BC. Instead of Block Headers, Hash and Merkle Proof, this type of “Oracle” package directly contains the cross-chain information for actions, such as sender, receiver and amount for transfer. 2. To ensure the security of the Oracle, the validators of BC will form anothe quorum of “**Oracle Relayers**”. Each validator of the BC should run a **dedicated process** as the Oracle Relayer. These Oracle Relayers will submit and vote for the cross-chain communication package, like Oracle, onto BC, using the same validator keys. Any package signed by more than ⅔\*N+1 Oracle Relayers’ voting power is as secure as any block signed by ⅔\*N+1 of the same quorum of validators’ voting power. By using the same validator quorum, it saves the light client code on BC and continuous block updates onto BC. Such Oracles also have Oracle IDs and types, to ensure sequencing and proper error handling. ## Timeout and Error Handling There are scenarios that the cross-chain communication fails. For example, the relayed package cannot be executed on BSC due to some coding bug in the contracts. **Timeout and error handling logics are** used in such scenarios. For the recognizable user and system errors or any expected exceptions, the two networks should heal themselves. For example, when BC to BSC transfer fails, BSC will issue a failure event and Oracle Relayers will execute a refund on BC; when BSC to BC transfer fails, BC will issue a refund package for Relayer to relay in order to unlock the fund. However, unexpected error or exception may still happen on any step of the cross-chain communication. In such a case, the Relayers and Oracle Relayers will discover that the corresponding cross-chain channel is stuck in a particular sequence. After a Timeout period, the Relayers and Oracle Relayers can request a “SkipSequence” transaction, the stuck sequence will be marked as “Unexecutable”. A corresponding alerts will be raised, and the community has to discuss how to handle this scenario, e.g. payback via the sponsor of the validators, or event clear the fund during next network upgrade. ## Cross-Chain User Experience Ideally, users expect to use two parallel chains in the same way as they use one single chain. It requires more aggregated transaction types to be added onto the cross-chain communication to enable this, which will add great complexity, tight coupling, and maintenance burden. Here BC and BSC only implement the basic operations to enable the value flow in the initial launch and leave most of the user experience work to client side UI, such as wallets. E.g. a great wallet may allow users to sell a token directly from BSC onto BC’s DEX order book, in a secure way. ## Cross-Chain Contract Event Cross-Chain Contract Event (CCCE) is designed to allow a smart contract to trigger cross-chain transactions, directly through the contract code. This becomes possible based on: 1. Standard system contracts can be provided to serve operations callable by general smart contracts; 2. Standard events can be emitted by the standard contracts; 3. Oracle Relayers can capture the standard events, and trigger the corresponding cross-chain operations; 4. Dedicated, code-managed address (account) can be created on BC and accessed by the contracts on the BSC, here it is named as **“Contract Address on BC” (CAoB)**. Several standard operations are implemented: 1. BSC to BC transfer: this is implemented in the same way as normal BSC to BC transfer, by only triggered via standard contract. The fund can be transferred to any addresses on BC, including the corresponding CAoB of the transfer originating contract. 2. Transfer on BC: this is implemented as a special cross-chain transfer, while the real transfer is from **CAoB** to any other address (even another CAoB). 3. BC to BSC transfer: this is implemented as two-pass cross-chain communication. The first is triggered by the BSC contract and propagated onto BC, and then in the second pass, BC will start a normal BC to BSC cross-chain transfer, from **CAoB** to contract address on BSC. A special note should be paid on that the BSC contract only increases balance upon any transfer coming in on the second pass, and the error handling in the second pass is the same as the normal BC to BSC transfer. 4. IOC (Immediate-Or-Cancel) Trade Out: the primary goal of transferring assets to BC is to trade. This event will instruct to trade a certain amount of an asset in CAoB into another asset as much as possible and transfer out all the results, i.e. the left the source and the traded target tokens of the trade, back to BSC. BC will handle such relayed events by sending an “Immediate-Or-Cancel”, i.e. IOC order onto the trading pairs, once the next matching finishes, the result will be relayed back to BSC, which can be in either one or two assets. 5. Auction Trade Out: Such event will instruct BC to send an auction order to trade a certain amount of an asset in **CAoB** into another asset as much as possible and transfer out all the results back to BSC at the end of the auction. Auction function is upcoming on BC. There are some details for the Trade Out: 1. both can have a limit price (absolute or relative) for the trade; 2. the end result will be written as cross-chain packages to relay back to BSC; 3. cross-chain communication fees may be charged from the asset transferred back to BSC; 4. BSC contract maintains a mirror of the balance and outstanding orders on CAoB. No matter what error happens during the Trade Out, the final status will be propagated back to the originating contract and clear its internal state. With the above features, it simply adds the cross-chain transfer and exchange functions with high liquidity onto all the smart contracts on BSC. It will greatly add the application scenarios on Smart Contract and dApps, and make 1 chain +1 chain > 2 chains. # Staking and Governance Proof of Staked Authority brings in decentralization and community involvement. Its core logic can be summarized as the below. You may see similar ideas from other networks, especially Cosmos and EOS. 1. Token holders, including the validators, can put their tokens “**bonded**” into the stake. Token holders can **delegate** their tokens onto any validator or validator candidate, to expect it can become an actual validator, and later they can choose a different validator or candidate to **re-delegate** their tokens<sup>1</sup>. 2. All validator candidates will be ranked by the number of bonded tokens on them, and the top ones will become the real validators. 3. Validators can share (part of) their blocking reward with their delegators. 4. Validators can suffer from “**Slashing**”, a punishment for their bad behaviors, such as double sign and/or instability. 5. There is an “**unbonding period**” for validators and delegators so that the system makes sure the tokens remain bonded when bad behaviors are caught, the responsible will get slashed during this period. ## Staking on BC Ideally, such staking and reward logic should be built into the blockchain, and automatically executed as the blocking happens. Cosmos Hub, who shares the same Tendermint consensus and libraries with Binance Chain, works in this way. BC has been preparing to enable staking logic since the design days. On the other side, as BSC wants to remain compatible with Ethereum as much as possible, it is a great challenge and efforts to implement such logic on it. This is especially true when Ethereum itself may move into a different Proof of Stake consensus protocol in a short (or longer) time. In order to keep the compatibility and reuse the good foundation of BC, the staking logic of BSC is implemented on BC: 1. The staking token is BNB, as it is a native token on both blockchains anyway 2. The staking, i.e. token bond and delegation actions and records for BSC, happens on BC. 3. The BSC validator set is determined by its staking and delegation logic, via a staking module built on BC for BSC, and propagated every day UTC 00:00 from BC to BSC via Cross-Chain communication. 4. The reward distribution happens on BC around every day UTC 00:00. ## Rewarding Both the validator update and reward distribution happen every day around UTC 00:00. This is to save the cost of frequent staking updates and block reward distribution. This cost can be significant, as the blocking reward is collected on BSC and distributed on BC to BSC validators and delegators. (Please note BC blocking fees will remain rewarding to BC validators only.) A deliberate delay is introduced here to make sure the distribution is fair: 1. The blocking reward will not be sent to validator right away, instead, they will be distributed and accumulated on a contract; 2. Upon receiving the validator set update into BSC, it will trigger a few cross-chain transfers to transfer the reward to custody addresses on the corresponding validators. The custody addresses are owned by the system so that the reward cannot be spent until the promised distribution to delegators happens. 3. In order to make the synchronization simpler and allocate time to accommodate slashing, the reward for N day will be only distributed in N+2 days. After the delegators get the reward, the left will be transferred to validators’ own reward addresses. ## Slashing Slashing is part of the on-chain governance, to ensure the malicious or negative behaviors are punished. BSC slash can be submitted by anyone. The transaction submission requires **slash evidence** and cost fees but also brings a larger reward when it is successful. So far there are two slashable cases. ### Double Sign It is quite a serious error and very likely deliberate offense when a validator signs more than one block with the same height and parent block. The reference protocol implementation should already have logic to prevent this, so only the malicious code can trigger this. When Double Sign happens, the validator should be removed from the Validator **Set** right away. Anyone can submit a slash request on BC with the evidence of Double Sign of BSC, which should contain the 2 block headers with the same height and parent block, sealed by the offending validator. Upon receiving the evidence, if the BC verifies it to be valid: 1. The validator will be removed from validator set by an instance BSC validator set update Cross-Chain update; 2. A predefined amount of BNB would be slashed from the **self-delegated** BNB of the validator; Both validator and its delegators will not receive the staking rewards. 3. Part of the slashed BNB will allocate to the submitter’s address, which is a reward and larger than the cost of submitting slash request transaction 4. The rest of the slashed BNB will allocate to the other validators’ custody addresses, and distributed to all delegators in the same way as blocking reward. ### Inavailability The liveness of BSC relies on everyone in the Proof of Staked Authority validator set can produce blocks timely when it is their turn. Validators can miss their turn due to any reason, especially problems in their hardware, software, configuration or network. This instability of the operation will hurt the performance and introduce more indeterministic into the system. There can be an internal smart contract responsible for recording the missed blocking metrics of each validator. Once the metrics are above the predefined threshold, the blocking reward for validator will not be relayed to BC for distribution but shared with other better validators. In such a way, the poorly-operating validator should be gradually voted out of the validator set as their delegators will receive less or none reward. If the metrics remain above another higher level of threshold, the validator will be dropped from the rotation, and this will be propagated back to BC, then a predefined amount of BNB would be slashed from the **self-delegated** BNB of the validator. Both validators and delegators will not receive their staking rewards. ### Governance Parameters There are many system parameters to control the behavior of the BSC, e.g. slash amount, cross-chain transfer fees. All these parameters will be determined by BSC Validator Set together through a proposal-vote process based on their staking. Such the process will be carried on BC, and the new parameter values will be picked up by corresponding system contracts via a cross-chain communication. # Relayers Relayers are responsible to submit Cross-Chain Communication Packages between the two blockchains. Due to the heterogeneous parallel chain structure, two different types of Relayers are created. ## BSC Relayers Relayers for BC to BSC communication referred to as “**BSC Relayers**”, or just simply “Relayers”. Relayer is a standalone process that can be run by anyone, and anywhere, except that Relayers must register themselves onto BSC and deposit a certain refundable amount of BNB. Only relaying requests from the registered Relayers will be accepted by BSC. The package they relay will be verified by the on-chain light client on BSC. The successful relay needs to pass enough verification and costs gas fees on BSC, and thus there should be incentive reward to encourage the community to run Relayers. ### Incentives There are two major communication types: 1. Users triggered Operations, such as `token bind` or `cross chain transfer`. Users must pay additional fee to as relayer reward. The reward will be shared with the relayers who sync the referenced blockchain headers. Besides, the reward won't be paid the relayers' accounts directly. A reward distribution mechanism will be brought in to avoid monopolization. 2. System Synchronization, such as delivering `refund package`(caused by failures of most oracle relayers), special blockchain header synchronization(header contains BC validatorset update), BSC staking package. System reward contract will pay reward to relayers' accounts directly. If some Relayers have faster networks and better hardware, they can monopolize all the package relaying and leave no reward to others. Thus fewer participants will join for relaying, which encourages centralization and harms the efficiency and security of the network. Ideally, due to the decentralization and dynamic re-election of BSC validators, one Relayer can hardly be always the first to relay every message. But in order to avoid the monopolization further, the rewarding economy is also specially designed to minimize such chance: 1. The reward for Relayers will be only distributed in batches, and one batch will cover a number of successful relayed packages. 2. The reward a Relayer can get from a batch distribution is not linearly in proportion to their number of successful relayed packages. Instead, except the first a few relays, the more a Relayer relays during a batch period, the less reward it will collect. ## Oracle Relayers Relayers for BSC to BC communication are using the “Oracle” model, and so-called “**Oracle Relayers**”. Each of the validators must, and only the ones of the validator set, run Oracle Relayers. Each Oracle Relayer watches the blockchain state change. Once it catches Cross-Chain Communication Packages, it will submit to vote for the requests. After Oracle Relayers from ⅔ of the voting power of BC validators vote for the changes, the cross-chain actions will be performed. Oracle Replayers should wait for enough blocks to confirm the finality on BSC before submitting and voting for the cross-chain communication packages onto BC. The cross-chain fees will be distributed to BC validators together with the normal BC blocking rewards. Such oracle type relaying depends on all the validators to support. As all the votes for the cross-chain communication packages are recorded on the blockchain, it is not hard to have a metric system to assess the performance of the Oracle Relayers. The poorest performer may have their rewards clawed back via another Slashing logic introduced in the future. # Outlook It is hard to conclude for Binance Chain, as it has never stopped evolving. The dual-chain strategy is to open the gate for users to take advantage of the fast transferring and trading on one side, and flexible and extendable programming on the other side, but it will be one stop along the development of Binance Chain. Here below are the topics to look into so as to facilitate the community better for more usability and extensibility: 1. Add different digital asset model for different business use cases 2. Enable more data feed, especially DEX market data, to be communicated from Binance DEX to BSC 3. Provide interface and compatibility to integrate with Ethereum, including its further upgrade, and other blockchain 4. Improve client side experience to manage wallets and use blockchain more conveniently ------ [1]: BNB business practitioners may provide other benefits for BNB delegators, as they do now for long term BNB holders.

Apache-2.0

Updated 2 weeks ago

Bayesian-Regression-to-Predict-Bitcoin-Price-Variations

aarivan

❤️30

predicting the price variations of bitcoin, a virtual cryptographic currency. These predictions could be used as the foundation of a bitcoin trading strategy. To make these predictions, you will have to familiarize yourself with a machine learning technique, Bayesian Regression, and implement this technique in Python

Python

Updated 9 months ago

The-Bitcoin-Foundation-Legal-Repo

pmlaw

❤️20

A public repo for legal documents related to The Bitcoin Foundation

Updated 8 months ago

Bayesian-Regression-and-Bitcoin

vkgnandhu177

❤️35

# Bayesian-Regression-to-Predict-Bitcoin-Price-Variations Predicting the price variations of bitcoin, a virtual cryptographic currency. These predictions could be used as the foundation of a bitcoin trading strategy. To make these predictions, we will have to familiarize ourself with a machine learning technique, Bayesian Regression, and implement this technique in Python. # Datasets We have the datasets in the data folder. The original raw data can be found here: http://api.bitcoincharts.com/v1/csv/. The datasets from this site have three attributes: (1) time in epoch, (2) price in USD per bitcoin, and (3) bitcoin amount in a transaction (buy/sell). However, only the first two attributes are relevant to this project. To make the data to have evenly space records, we took all the records within a 20 second window and replaced it by a single record as the average of all the transaction prices in that window. Not every 20 second window had a record; therefore those missing entries were filled using the prices of the previous 20 observations and assuming a Gaussian distribution. The raw data that has been cleaned is given in the file dataset.csv Finally, as discussed in the paper, the data was divided into a total of 9 different datasets. The whole dataset is partitioned into three equally sized (50 price variations in each) subsets: train1, train2, and test. The train sets are used for training a linear model, while the test set is for evaluation of the model. There are three csv files associated with each subset of data: *_90.csv, *_180.csv, and *_360.csv. In _90.csv, for example, each line represents a vector of length 90 where the elements are 30 minute worth of bitcoin price variations (since we have 20 second intervals) and a price variation in the 91st column. Similarly, the *_180.csv represents 60 minutes of prices and *_360.csv represents 120 minutes of prices. # Project Requirements We are expected to implement the Bayesian Regression model to predict the future price variation of bitcoin as described in the reference paper. The main parts to focus on are Equation 6 and the Predicting Price Change section. # Logic in bitcoin.py 1. Compute the price variations (Δp1, Δp2, and Δp3) for train2 using train1 as input to the Bayesian Regression equation (Equations 6). Make sure to use the similarity metric (Equation 9) in place of the Euclidean distance in Bayesian Regression (Equation 6). 2. Compute the linear regression parameters (w0, w1, w2, w3) by finding the best linear fit (Equation 8). Here you will need to use the ols function of statsmodels.formula.api. Your model should be fit using Δp1, Δp2, and Δp3 as the covariates. Note: the bitcoin order book data was not available, so you do not have to worry about the rw4 term. 3. Use the linear regression model computed in Step 2 and Bayesian Regression estimates, to predict the price variations for the test dataset. Bayesian Regression estimates for test dataset are computed in the same way as they are computed for train2 dataset – using train1 as an input. 4. Once the price variations are predicted, compute the mean squared error (MSE) for the test dataset (the test dataset has 50 vectors => 50 predictions).

Python

Updated 5 months ago

bitcoin-ngo-guide

lcuen

❤️40

This is an editable version of the nonprofit guide commissioned by the Human Rights Foundation in cooperation with the Bitcoin Policy Institute

MIT

Updated 1 year ago

bitcoinnonprofits

Bitcoin-Foundation

uvhw

🧡60

Bitcoin: A Peer-to-Peer Electronic Cash System Satoshi Nakamoto satoshin@gmx.com www.bitcoin.org Abstract. A purely peer-to-peer version of electronic cash would allow online payments to be sent directly from one party to another without going through a financial institution. Digital signatures provide part of the solution, but the main benefits are lost if a trusted third party is still required to prevent double-spending. We propose a solution to the double-spending problem using a peer-to-peer network. The network timestamps transactions by hashing them into an ongoing chain of hash-based proof-of-work, forming a record that cannot be changed without redoing the proof-of-work. The longest chain not only serves as proof of the sequence of events witnessed, but proof that it came from the largest pool of CPU power. As long as a majority of CPU power is controlled by nodes that are not cooperating to attack the network, they'll generate the longest chain and outpace attackers. The network itself requires minimal structure. Messages are broadcast on a best effort basis, and nodes can leave and rejoin the network at will, accepting the longest proof-of-work chain as proof of what happened while they were gone. 1. Introduction Commerce on the Internet has come to rely almost exclusively on financial institutions serving as trusted third parties to process electronic payments. While the system works well enough for most transactions, it still suffers from the inherent weaknesses of the trust based model. Completely non-reversible transactions are not really possible, since financial institutions cannot avoid mediating disputes. The cost of mediation increases transaction costs, limiting the minimum practical transaction size and cutting off the possibility for small casual transactions, and there is a broader cost in the loss of ability to make non-reversible payments for non- reversible services. With the possibility of reversal, the need for trust spreads. Merchants must be wary of their customers, hassling them for more information than they would otherwise need. A certain percentage of fraud is accepted as unavoidable. These costs and payment uncertainties can be avoided in person by using physical currency, but no mechanism exists to make payments over a communications channel without a trusted party. What is needed is an electronic payment system based on cryptographic proof instead of trust, allowing any two willing parties to transact directly with each other without the need for a trusted third party. Transactions that are computationally impractical to reverse would protect sellers from fraud, and routine escrow mechanisms could easily be implemented to protect buyers. In this paper, we propose a solution to the double-spending problem using a peer-to-peer distributed timestamp server to generate computational proof of the chronological order of transactions. The system is secure as long as honest nodes collectively control more CPU power than any cooperating group of attacker nodes. 1 2. Transactions We define an electronic coin as a chain of digital signatures. Each owner transfers the coin to the next by digitally signing a hash of the previous transaction and the public key of the next owner and adding these to the end of the coin. A payee can verify the signatures to verify the chain of ownership. Transaction Hash Transaction Hash Transaction Hash Owner 1's Public Key Owner 2's Public Key Owner 3's Public Key Owner 0's Signature Owner 1's Signature The problem of course is the payee can't verify that one of the owners did not double-spend the coin. A common solution is to introduce a trusted central authority, or mint, that checks every transaction for double spending. After each transaction, the coin must be returned to the mint to issue a new coin, and only coins issued directly from the mint are trusted not to be double-spent. The problem with this solution is that the fate of the entire money system depends on the company running the mint, with every transaction having to go through them, just like a bank. We need a way for the payee to know that the previous owners did not sign any earlier transactions. For our purposes, the earliest transaction is the one that counts, so we don't care about later attempts to double-spend. The only way to confirm the absence of a transaction is to be aware of all transactions. In the mint based model, the mint was aware of all transactions and decided which arrived first. To accomplish this without a trusted party, transactions must be publicly announced [1], and we need a system for participants to agree on a single history of the order in which they were received. The payee needs proof that at the time of each transaction, the majority of nodes agreed it was the first received. 3. Timestamp Server The solution we propose begins with a timestamp server. A timestamp server works by taking a hash of a block of items to be timestamped and widely publishing the hash, such as in a newspaper or Usenet post [2-5]. The timestamp proves that the data must have existed at the time, obviously, in order to get into the hash. Each timestamp includes the previous timestamp in its hash, forming a chain, with each additional timestamp reinforcing the ones before it. Hash Hash Owner 2's Signature Owner 1's Private Key Owner 2's Private Key Owner 3's Private Key Block Item Item ... 2 Block Item Item ... Verify Verify Sign Sign 4. Proof-of-Work To implement a distributed timestamp server on a peer-to-peer basis, we will need to use a proof- of-work system similar to Adam Back's Hashcash [6], rather than newspaper or Usenet posts. The proof-of-work involves scanning for a value that when hashed, such as with SHA-256, the hash begins with a number of zero bits. The average work required is exponential in the number of zero bits required and can be verified by executing a single hash. For our timestamp network, we implement the proof-of-work by incrementing a nonce in the block until a value is found that gives the block's hash the required zero bits. Once the CPU effort has been expended to make it satisfy the proof-of-work, the block cannot be changed without redoing the work. As later blocks are chained after it, the work to change the block would include redoing all the blocks after it. The proof-of-work also solves the problem of determining representation in majority decision making. If the majority were based on one-IP-address-one-vote, it could be subverted by anyone able to allocate many IPs. Proof-of-work is essentially one-CPU-one-vote. The majority decision is represented by the longest chain, which has the greatest proof-of-work effort invested in it. If a majority of CPU power is controlled by honest nodes, the honest chain will grow the fastest and outpace any competing chains. To modify a past block, an attacker would have to redo the proof-of-work of the block and all blocks after it and then catch up with and surpass the work of the honest nodes. We will show later that the probability of a slower attacker catching up diminishes exponentially as subsequent blocks are added. To compensate for increasing hardware speed and varying interest in running nodes over time, the proof-of-work difficulty is determined by a moving average targeting an average number of blocks per hour. If they're generated too fast, the difficulty increases. 5. Network The steps to run the network are as follows: 1) New transactions are broadcast to all nodes. 2) Each node collects new transactions into a block. 3) Each node works on finding a difficult proof-of-work for its block. 4) When a node finds a proof-of-work, it broadcasts the block to all nodes. 5) Nodes accept the block only if all transactions in it are valid and not already spent. 6) Nodes express their acceptance of the block by working on creating the next block in the chain, using the hash of the accepted block as the previous hash. Nodes always consider the longest chain to be the correct one and will keep working on extending it. If two nodes broadcast different versions of the next block simultaneously, some nodes may receive one or the other first. In that case, they work on the first one they received, but save the other branch in case it becomes longer. The tie will be broken when the next proof- of-work is found and one branch becomes longer; the nodes that were working on the other branch will then switch to the longer one. 3 Block Nonce Tx Tx ... Block Nonce Tx Tx ... Prev Hash Prev Hash New transaction broadcasts do not necessarily need to reach all nodes. As long as they reach many nodes, they will get into a block before long. Block broadcasts are also tolerant of dropped messages. If a node does not receive a block, it will request it when it receives the next block and realizes it missed one. 6. Incentive By convention, the first transaction in a block is a special transaction that starts a new coin owned by the creator of the block. This adds an incentive for nodes to support the network, and provides a way to initially distribute coins into circulation, since there is no central authority to issue them. The steady addition of a constant of amount of new coins is analogous to gold miners expending resources to add gold to circulation. In our case, it is CPU time and electricity that is expended. The incentive can also be funded with transaction fees. If the output value of a transaction is less than its input value, the difference is a transaction fee that is added to the incentive value of the block containing the transaction. Once a predetermined number of coins have entered circulation, the incentive can transition entirely to transaction fees and be completely inflation free. The incentive may help encourage nodes to stay honest. If a greedy attacker is able to assemble more CPU power than all the honest nodes, he would have to choose between using it to defraud people by stealing back his payments, or using it to generate new coins. He ought to find it more profitable to play by the rules, such rules that favour him with more new coins than everyone else combined, than to undermine the system and the validity of his own wealth. 7. Reclaiming Disk Space Once the latest transaction in a coin is buried under enough blocks, the spent transactions before it can be discarded to save disk space. To facilitate this without breaking the block's hash, transactions are hashed in a Merkle Tree [7][2][5], with only the root included in the block's hash. Old blocks can then be compacted by stubbing off branches of the tree. The interior hashes do not need to be stored. Block Hash0 Hash1 Hash2 Hash3 Tx0 Tx1 Tx2 Tx3 Block Header (Block Hash) Prev Hash Nonce Root Hash Hash01 Hash23 Block Block Header (Block Hash) Prev Hash Nonce Root Hash Hash01 Hash23 Hash2 Hash3 Tx3 Transactions Hashed in a Merkle Tree After Pruning Tx0-2 from the Block A block header with no transactions would be about 80 bytes. If we suppose blocks are generated every 10 minutes, 80 bytes * 6 * 24 * 365 = 4.2MB per year. With computer systems typically selling with 2GB of RAM as of 2008, and Moore's Law predicting current growth of 1.2GB per year, storage should not be a problem even if the block headers must be kept in memory. 4 8. Simplified Payment Verification It is possible to verify payments without running a full network node. A user only needs to keep a copy of the block headers of the longest proof-of-work chain, which he can get by querying network nodes until he's convinced he has the longest chain, and obtain the Merkle branch linking the transaction to the block it's timestamped in. He can't check the transaction for himself, but by linking it to a place in the chain, he can see that a network node has accepted it, and blocks added after it further confirm the network has accepted it. Longest Proof-of-Work Chain Block Header Block Header Block Header Prev Hash Nonce Prev Hash Nonce Prev Hash Nonce Merkle Root Merkle Root Merkle Root Hash01 Hash23 Merkle Branch for Tx3 Hash2 Hash3 Tx3 As such, the verification is reliable as long as honest nodes control the network, but is more vulnerable if the network is overpowered by an attacker. While network nodes can verify transactions for themselves, the simplified method can be fooled by an attacker's fabricated transactions for as long as the attacker can continue to overpower the network. One strategy to protect against this would be to accept alerts from network nodes when they detect an invalid block, prompting the user's software to download the full block and alerted transactions to confirm the inconsistency. Businesses that receive frequent payments will probably still want to run their own nodes for more independent security and quicker verification. 9. Combining and Splitting Value Although it would be possible to handle coins individually, it would be unwieldy to make a separate transaction for every cent in a transfer. To allow value to be split and combined, transactions contain multiple inputs and outputs. Normally there will be either a single input from a larger previous transaction or multiple inputs combining smaller amounts, and at most two outputs: one for the payment, and one returning the change, if any, back to the sender. It should be noted that fan-out, where a transaction depends on several transactions, and those transactions depend on many more, is not a problem here. There is never the need to extract a complete standalone copy of a transaction's history. 5 Transaction In Out In ... ... 10. Privacy The traditional banking model achieves a level of privacy by limiting access to information to the parties involved and the trusted third party. The necessity to announce all transactions publicly precludes this method, but privacy can still be maintained by breaking the flow of information in another place: by keeping public keys anonymous. The public can see that someone is sending an amount to someone else, but without information linking the transaction to anyone. This is similar to the level of information released by stock exchanges, where the time and size of individual trades, the "tape", is made public, but without telling who the parties were. Traditional Privacy Model Identities Transactions New Privacy Model Identities Transactions As an additional firewall, a new key pair should be used for each transaction to keep them from being linked to a common owner. Some linking is still unavoidable with multi-input transactions, which necessarily reveal that their inputs were owned by the same owner. The risk is that if the owner of a key is revealed, linking could reveal other transactions that belonged to the same owner. 11. Calculations We consider the scenario of an attacker trying to generate an alternate chain faster than the honest chain. Even if this is accomplished, it does not throw the system open to arbitrary changes, such as creating value out of thin air or taking money that never belonged to the attacker. Nodes are not going to accept an invalid transaction as payment, and honest nodes will never accept a block containing them. An attacker can only try to change one of his own transactions to take back money he recently spent. The race between the honest chain and an attacker chain can be characterized as a Binomial Random Walk. The success event is the honest chain being extended by one block, increasing its lead by +1, and the failure event is the attacker's chain being extended by one block, reducing the gap by -1. The probability of an attacker catching up from a given deficit is analogous to a Gambler's Ruin problem. Suppose a gambler with unlimited credit starts at a deficit and plays potentially an infinite number of trials to try to reach breakeven. We can calculate the probability he ever reaches breakeven, or that an attacker ever catches up with the honest chain, as follows [8]: p = probability an honest node finds the next block q = probability the attacker finds the next block qz = probability the attacker will ever catch up from z blocks behind Trusted Third Party q ={ 1 if p≤q} z q/pz if pq 6 Counterparty Public Public Given our assumption that p > q, the probability drops exponentially as the number of blocks the attacker has to catch up with increases. With the odds against him, if he doesn't make a lucky lunge forward early on, his chances become vanishingly small as he falls further behind. We now consider how long the recipient of a new transaction needs to wait before being sufficiently certain the sender can't change the transaction. We assume the sender is an attacker who wants to make the recipient believe he paid him for a while, then switch it to pay back to himself after some time has passed. The receiver will be alerted when that happens, but the sender hopes it will be too late. The receiver generates a new key pair and gives the public key to the sender shortly before signing. This prevents the sender from preparing a chain of blocks ahead of time by working on it continuously until he is lucky enough to get far enough ahead, then executing the transaction at that moment. Once the transaction is sent, the dishonest sender starts working in secret on a parallel chain containing an alternate version of his transaction. The recipient waits until the transaction has been added to a block and z blocks have been linked after it. He doesn't know the exact amount of progress the attacker has made, but assuming the honest blocks took the average expected time per block, the attacker's potential progress will be a Poisson distribution with expected value:  = z qp To get the probability the attacker could still catch up now, we multiply the Poisson density for each amount of progress he could have made by the probability he could catch up from that point: ∞ ke−{q/pz−k ifk≤z} ∑k=0 k!⋅ 1 ifkz Rearranging to avoid summing the infinite tail of the distribution... z ke− z−k 1−∑k=0 k! 1−q/p  Converting to C code... #include <math.h> double AttackerSuccessProbability(double q, int z) { double p = 1.0 - q; double lambda = z * (q / p); double sum = 1.0; int i, k; for (k = 0; k <= z; k++) { double poisson = exp(-lambda); for (i = 1; i <= k; i++) poisson *= lambda / i; sum -= poisson * (1 - pow(q / p, z - k)); } return sum; } 7 Running some results, we can see the probability drop off exponentially with z. q=0.1 z=0 P=1.0000000 z=1 P=0.2045873 z=2 P=0.0509779 z=3 P=0.0131722 z=4 P=0.0034552 z=5 P=0.0009137 z=6 P=0.0002428 z=7 P=0.0000647 z=8 P=0.0000173 z=9 P=0.0000046 z=10 P=0.0000012 q=0.3 z=0 P=1.0000000 z=5 P=0.1773523 z=10 P=0.0416605 z=15 P=0.0101008 z=20 P=0.0024804 z=25 P=0.0006132 z=30 P=0.0001522 z=35 P=0.0000379 z=40 P=0.0000095 z=45 P=0.0000024 z=50 P=0.0000006 Solving for P less than 0.1%... P < 0.001 q=0.10 z=5 q=0.15 z=8 q=0.20 z=11 q=0.25 z=15 q=0.30 z=24 q=0.35 z=41 q=0.40 z=89 q=0.45 z=340 12. Conclusion We have proposed a system for electronic transactions without relying on trust. We started with the usual framework of coins made from digital signatures, which provides strong control of ownership, but is incomplete without a way to prevent double-spending. To solve this, we proposed a peer-to-peer network using proof-of-work to record a public history of transactions that quickly becomes computationally impractical for an attacker to change if honest nodes control a majority of CPU power. The network is robust in its unstructured simplicity. Nodes work all at once with little coordination. They do not need to be identified, since messages are not routed to any particular place and only need to be delivered on a best effort basis. Nodes can leave and rejoin the network at will, accepting the proof-of-work chain as proof of what happened while they were gone. They vote with their CPU power, expressing their acceptance of valid blocks by working on extending them and rejecting invalid blocks by refusing to work on them. Any needed rules and incentives can be enforced with this consensus mechanism. 8 References [1] W. Dai, "b-money," http://www.weidai.com/bmoney.txt, 1998. [2] H. Massias, X.S. Avila, and J.-J. Quisquater, "Design of a secure timestamping service with minimal trust requirements," In 20th Symposium on Information Theory in the Benelux, May 1999. [3] S. Haber, W.S. Stornetta, "How to time-stamp a digital document," In Journal of Cryptology, vol 3, no 2, pages 99-111, 1991. [4] D. Bayer, S. Haber, W.S. Stornetta, "Improving the efficiency and reliability of digital time-stamping," In Sequences II: Methods in Communication, Security and Computer Science, pages 329-334, 1993. [5] S. Haber, W.S. Stornetta, "Secure names for bit-strings," In Proceedings of the 4th ACM Conference on Computer and Communications Security, pages 28-35, April 1997. [6] A. Back, "Hashcash - a denial of service counter-measure," http://www.hashcash.org/papers/hashcash.pdf, 2002. [7] R.C. Merkle, "Protocols for public key cryptosystems," In Proc. 1980 Symposium on Security and Privacy, IEEE Computer Society, pages 122-133, April 1980. [8] W. Feller, "An introduction to probability theory and its applications," 1957. 9

MIT

C++

Updated 3 weeks ago

crypto_dice_site

Wysie

❤️35

This is a fair dice site including the verifier so you can see that the results are fair and not tampered with. I wrote this as a way for me to learn Tornado. In addition, I'm using KnockoutJS, jQuery, Foundation and SockJS. Lots of other Python libraries were used too, such as bitcoin-python to handle the RPC calls to the coin daemon. Database-wise, it's running off PostgreSQL, using momoko to connect to it from Tornado for async DB calls. Here is one of the sites I have running this code: http://coindice.supercrypt.co. As I'm no longer actively maintaining those sites, I decided to put this up on Github publicly in case anyone is interested. Have fun :)! Just for information, most of the content still references Aiden dice, which is one of the latest dice sites I've built.

JavaScript

Updated 1 year ago

Ethereum-Mainnet-chainld-2-short-Name-ethereum-mahmood-monfared

Mahmoodmonfared

🧡55

Unlicense

Updated 1 day ago

Gcoin

Gcoin-project

❤️40

GCOIN is a free open source project derived from Bitcoin, with the goal of providing a long-term energy-efficent scrypt-based crypto-currency. Built on the foundation of Bitcoin, PPCoin and NovaCoin, innovations such as proof-of-stake and scrypt help further advance the field of crypto-currency.

MIT

TypeScript

Updated 4 years ago

MaxCoin

BlockchainLabs

❤️35

There is a lot of uncertainty about of Bitcoin, so many turn to the altcoin market to diversity their crypto holdings, only to find more uncertainty. CoinMarketCap lists over 500 coins, and there are probably more. In this brief post, I offer Maxcoin’s qualifications as a worthy investment and trade currency. Maxcoin has a dedicated, skilled, and cognizant foundation team that understands both the economics and politics of cryptocurrency. Crypto is not just a faster and cheaper payment method and a more secure store of value, it’s about decentralizing the use of currency by removing it from the establishment’s monopoly. Cryptocurrency allows you to buy and sell and give and save apart from state and bank run spy grids and theft rings. Because you own your coins which are transacted with high cryptography on a decentralized public blockchain, there are no extortionate fees, bank runs, frozen accounts, bailouts, or financial surveillance. The Maxcoin team understands the importance of using your coins in privacy and with security. Our team members also have a various skill from their professional backgrounds in system administration, programming, web design, technical writing, project management, quality assurance, market trading, and others. More important is their enthusiastic entrepreneurship and dedication to expanding and enriching the Maxcoin ecosystem. Our team members spend countless unpaid hours of planning and building for Maxcoin. Learn more about our team here. We believe Maxcoin has basic advantages that distinguish it from other altcoins. Here are a few: Fundamentals Stronger encryption (SHA3), faster transactions (1 minute block time), low inflation (16 coins per block) Budding Maxcoin Foundation with a roadmap to self-sustainability A one-of-a-kind Maxcoin Bounty Program that allows you to anonymously and immediately donate MAX and BTC to crowdsource the development of Maxcoin’s critical infrastructure and ecosystem Markets and Services Listed on 7 exchanges including Cryptsy, Bittrex, Bittylicious, and BTER with 4 currency pairs Revolutionary Cryptobullion (startjoin.com/maxcoinbullion) that will soon be available from selected bullion dealers. Maxcoin can be spent anywhere Bitcoin is accepted through Coingateway.net Buy over 150 gift cards with Maxcoin (Pock.io) Maxcoin Gambling (Cryptobetfair.com) Integration into multicurrency wallet at Casheer.net, Oct 2015 Community and Exposure Exposure to over 9,000 followers on twitter, more than Ripple, Darkcoin, NXT and many others with more market cap. Maxcoin Forums (forum.maxcoin.co.uk) and chat (maxchat.info) Other communication channels available at Facebook and Bitcointalk This list of distinguishing characteristics doesn’t change the market price overnight. Like many coins, Maxcoin has seen its share of malicious miners, speculative day traders, and committed internet trolls. These people are either jealous of the above points or simply foolish and enjoy throwing away treasure. Yes, we are biased, but we genuinely think that Maxcoin is a bargain wonder coin. On the markets, it is at historic lows. But objectively, given its present facts and future goals, Maxcoin is at historic highs. | WHY MAXCOIN MAXCOIN IS MONEY WITHOUT BANKS. USING MAXCOIN, YOU CAN INSTANTLY, SECURELY AND FOR FREE SEND AND RECEIVE PAYMENTS TO FRIENDS, FAMILY AND MERCHANTS WORLDWIDE. A NEW APPROACH TO INNOVATION MaxCoin is one of the most secure crypto currencies, both because it's based on next generation encryption, SHA3, but also because it's 'open source'. MaxCoin's software is open to inspection and improvement by the best security minds on the planet so that it's mathematically secure. If you don't like paying bank charges, if you don't like the way money is created by banks at no cost to them, and then loaned out to us with interest, then MaxCoin is paving the way to a new money. Open, transparent, and free of charge. Learn more... • Algorithm: Keccak (SHA-3) • Generation: 100 million MAX • Block time: 1 minute • Block Rewards: 16 coins per block • Halving every ~4 years • Premine: Zero – not premined • Fees: Zero – no transaction fees • Difficulty: Retargets every block

Updated 2 years ago

whitepaper

peacockbsc

❤️20

1 Introduction As human beings we are usually first exposed to the gift economy of our families and tight knit communities: goods and services are provided without an explicit agreement for immediate or future rewards, but the exchange of love, kindness, and confidence. As the relationship circle is enlarged this mutual trust weakens, but the urge and willingness to cooperate does not diminish: this is when the need for an exchange economy arises. [Hayek Money: The Cryptocurrency Price Stability Solution] Cryptocurrency is a digital asset and becoming popular after the success of different crypto tokens in the market. The main technology behind the development and success of cryptocurrencies is blockchain technology. This modern technology work on the principle of decentralization. It provides better security, safety, and privacy. It reduces the risk of business and allows transparency with the key feature of decentralization. The memes Tokens gained fame in the 2021 bull market where currencies such as Dogecoin and Shiba inu hit market capitalization billions, turning thousands of small investors into millionaires in a matter of months.Turning into a real fever, accompanied by major marketing campaigns. 1.1 Blockchain Infrastructure Blockchain Technology can enhance the basic services that are essential in traditional finance and it has the potential to become the foundation for decentralized business models, empowering entrepreneurs and innovators with all the right tools. By means of a trustless and distributed infrastructure, blockchain technology is optimizing transactional costs and allows the rise of decentralized, innovative, inter-operable, borderless and transparent applications which facilitate open access and encourage permissionless innovations. [Bitcoin: A Peer-To-Peer Electronic Cash System (2009)]. Binance Smart Chain (BSC) is a blockchain that was developed as a means of utilizing solidity-based smart contracts with much greater speed and efficiency than other, competing chains. With decentralized exchanges on BSC offering lightning-fast swaps and extremely low fees, BSC has started to become one of the most widely used blockchains for Decentralized Finance (Defi). BSC uses a token protocol developed by the Binance Team called BEP-20. Binance Smart Chain is unique for several reasons: • It’s a sovereign blockchain, which will provide security and safety to all users and developers. • Its native dual chain interoperability will allow cross-chain communication and scaling of high-performance dApps that require a fast and smooth user experience • It’s EVM-compatible and will support all of the existing Ethereum toolings along with faster and cheaper transactions. • on-chain governance with Proof of Staked Authority consensus, built on 21 validators who validate the transactions, will provide decentralization and enable significant community involvement. 2 What is PEACOCK? ”When you come to the appointed place at the appointed time and meet some person, introduce yourself as Peacock. If they do the same, then you have met a special person.” - Peacock Token is a fan-driven deflationary meme token that came to dominate the meme game. appears as the father of Shiba Inu, the real Dogecoin Killer, is a deflationary BEP20 token that aims to propose an alternative to Dogecoin’s infinite supply and be an improved version of Shiba Inu, without the high fees of the ethereum network, protection against damage from diving and preventing dumping of whales. After each transaction there is a 10% burnout, this is to supply and increase demand, you can relax and watch your Peacock investment grow, the community aims to establish itself as Smart Chain’s biggest token meme our goal is to build a strong squad that will HODL their Peacock and never sell, with the aim of bringing the price of Peacock to a $1 dollar. Do not be greedy, we need all the support from the community so that you never sell all your Peacock at the same time, due to the demand there may not be liquidity available making its value fall, when you believe it is necessary, just remove the invested amount, let’s make this the first meme coin to reach $1. 2.1 Tokenomics Peacock is a token that has an inelastic supply, which means that each transaction made, its offer is reduced in order to add value to the asset. To ensure a fair distribuition we have decided to burn 50% of the total supply. 42% of the supply is currentyly serving a life sentence at PancakeSwap correctional facility and is never getting out an 8% for Marketing and Dev team. • Total Supply: 420,000,000,000,000,000,000,000,000 • 50% Tokens Burnt Wallet: 0x000000000000000000000000000000000000dead • 42% locked in Pancakeswap Pancakeswap Address: 0x52F778A1E1c12C5520Be9a31511a8A256F0b1065 • 8% Team wallet Dev wallet: 0xe4b8141Ef61f7eb8601b71399aF7855256d1c414 Marketing wallet: 0x1dC6d1c6d518B409CcdeDb256b2a0296Ac263e0d Exchange liquidity: 0x12B08D7FA6C0913809EAE575FdDeC61f84aCABaD • 10% of fees burned with each transaction. Figure 1: 3 Community Our main objective is to build a strong community, where people from all over the world can exchange experiences and debate issues of global interest, using Peacock as a utility token. If a community is well maintained and constantly expanded, this can result ina trusting relationship between the target group and the Peacock, which can lay the foundation for loyal and stable repeat users. 3.1 Dip Damage Protection We have designed a Dip Damage Protection Mechanism Wallet where people from the community can contribute anything above $10 in BNB (BEP20) to make the protection stronger, so no whales will be able to beat our protection, members will be able to see all the transactions on blockchain happening in the Dip Damage Protection wallet. 3.2 Warning PEACOCK tokens is purely entertainment, not an investment. Purely an experimental GAME. Before purchasing PEACOCK tokens, you must ensure that the nature, complexity, and risks inherent in the trading of cryptocurrency are suitable for your objectives in light of your circumstances and financial position. You should only purchase PEACOCK to have fun and to experience this experimental game with us. Many factors outside of the control of PEACOCK Token will affect the market price, including, but not limited to, national and international economic, financial, regulatory, political, terrorist, military, and other events, adverse or positive news events and publicity, and generally extreme, uncertain, and volatile market conditions. Extreme changes in price may occur at any time, resulting in a potential loss of value, complete or partial loss of purchasing power, and difficulty, or a complete inability to sell or exchange your digital currency. PEACOCK tokens shall be under no obligation to purchase or to broker the purchase back from you of your cryptocurrency in circumstances where there is no viable market for the purchase of the same. None of the content published in this paper constitutes a recommendation that any particular cryptocurrency, portfolio of cryptocurrencies, transaction, or investment strategy is suitable for any specific person. None of the information providers or their affiliates will advise you personally concerning the nature, potential, value, or suitability of any particular cryptocurrency, portfolio of cryptocurrencies, transaction, investment strategy, or other matter. The products and services presented may only be purchased in jurisdictions in which their marketing and distribution are authorized. Play at your own risk and may the odds be ever in your favor. References BITCOIN: A PEER-TO-PEER ELECTRONIC CASH SYSTEM. Internet: Satoshi Nakamoto, v. 1, 2009. Dispon´ıvel em: https://bitcoin.org/bitcoin.pdf. Acesso em: 30 maio 2021. WANG, Qin; LI, Rujia; WANG, Qi; CHEN, Shiping. Non-Fungible Token (NFT): Overview, Evaluation, Opportunities and Challenges. Arxiv.Org, [s. l], p. 1-1, 2021. Cornel University. Dispon´ıvel em: 2105.07447. Acesso em: 30 maio 2021. Hayek Money: The Cryptocurrency Price Stability Solution

Updated 4 months ago

Bitcoin-Technical-Foundations

LibreriadeSatoshi

🧡50

Curricula

MIT

Updated 1 month ago

5G

5G-Cash

❤️25

5G-CASH (VGC) is the fifth-generation, open-source hybrid privacy-focused cryptocurrency with PoW, PoS, Masternodes, Dandelion++, and Tor integration. Designed for privacy and real-world utility. It's built on a robust Bitcoin Core foundation with enhanced consensus rules integrating anonymity tools to deliver a secure and scalable payment network.

MIT

Updated 3 months ago

blockchaincryptocurrencyprivacy

bitcoin_foundation

BP-WG

❤️15

Crates implementing the foundations of Bitcoin protocol

Rust

Updated 7 months ago

Karma

KeKo6988

❤️35

[ { "name": "Ethereum Mainnet", "chainId": 1, "shortName": "eth", "chain": "ETH", "network": "mainnet", "networkId": 1, "nativeCurrency": {"name": "Ether", "symbol": "ETH", "decimals": 18}, "rpc": ["https://mainnet.infura.io/v3/${INFURA_API_KEY}","wss://mainnet.infura.io/ws/v3/${INFURA_API_KEY}","https:// api.mycryptoapi.com/eth","https://cloudflare-eth.com "], "faucets": [], "explorers": [{"name": "etherscan", "url": "https://etherscan.io", "standard": "EIP3091"}], "infoURL": "https://ethereum.org" }, { "name": "Ethereum ottimista", "chainId": 10, "shortName": "oeth", "chain": "ETH", "network": "mainnet", "networkId": 10, "nativeCurrency": {"name": "Ether", "symbol": "OETH", "decimals": 18}, "rpc": ["https://mainnet.optimism.io/"], "faucets": [], "esploratori": [], "infoURL": "https://optimism.io" }, { "nome": "Catena xDAI", "chainId": 100, "shortName": "xdai", "catena": "XDAI", "network": "mainnet", "networkId": 100, "nativeCurrency": {"name": "xDAI", "symbol": "xDAI", "decimals": 18}, "rpc": ["https://rpc.xdaichain.com", "https://xdai.poanetwork.dev", "wss: //rpc.xdaichain.com/wss", "wss: // xdai. poanetwork.dev/wss","http://xdai.poanetwork.dev","https://dai.poa.network","ws://xdai.poanetwork.dev:8546 "], "faucets": [], "esploratori": [], "infoURL": "https://forum.poa.network/c/xdai-chain" }, { "nome": "Smart Bitcoin Cash", "chainId": 10000, "shortName": "smartbch", "chain": "smartBCH", "network": "mainnet", "networkId": 10000, "nativeCurrency": {"name": "Bitcoin Cash", "symbol": "BCH", "decimals": 18}, "rpc": ["https://rpc-mainnet.smartbch.org"], "faucets": [], "esploratori": [], "infoURL": "http://smartbch.org/" }, { "nome": "Smart Bitcoin Cash Testnet", "chainId": 10001, "shortName": "smartbchtest", "chain": "smartBCHTest", "network": "testnet", "networkId": 10001, "nativeCurrency": {"name": "Bitcoin Cash Test Token", "symbol": "BCHT", "decimals": 18}, "rpc": ["https://rpc-testnet.smartbch.org"], "faucets": [], "esploratori": [], "infoURL": "http://smartbch.org/" }, { "name": "Klaytn Testnet Baobab", "chainId": 1001, "shortName": "Baobab", "chain": "KLAY", "network": "baobab", "networkId": 1001, "nativeCurrency": {"name": "KLAY", "symbol": "KLAY", "decimals": 18}, "rpc": ["https://node-api.klaytnapi.com/v1/klaytn"], "faucets": ["https://baobab.wallet.klaytn.com/access?next=faucet"], "esploratori": [], "infoURL": "https://www.klaytn.com/" }, { "nome": "Newton Testnet", "chainId": 1007, "shortName": "tnew", "chain": "NEW", "network": "testnet", "networkId": 1007, "nativeCurrency": {"name": "Newton", "symbol": "NEW", "decimals": 18}, "rpc": ["https://rpc1.newchain.newtonproject.org"], "faucets": [], "esploratori": [], "infoURL": "https://www.newtonproject.org/" }, { "nome": "EtherInc", "chainId": 101, "shortName": "eti", "chain": "ETI", "network": "mainnet", "networkId": 1, "nativeCurrency": {"name": "EtherInc Ether", "symbol": "ETI", "decimals": 18}, "rpc": ["https://api.einc.io/jsonrpc/mainnet"], "faucets": [], "esploratori": [], "infoURL": "https://einc.io" }, { "name": "Evrice Network", "chainId": 1010, "shortName": "EVC", "chain": "EVC", "network": "Evrice", "networkId": 1010, "nativeCurrency": {"name": "Evrice", "symbol": "EVC", "decimals": 18}, "rpc": ["https://meta.evrice.com"], "faucets": [], "esploratori": [], "infoURL": "https://evrice.com" }, { "name": "Blockchain Genesis Mainnet", "chainId": 10101, "shortName": "GEN", "chain": "GEN", "network": "mainnet", "networkId": 10101, "nativeCurrency": {"name": "GEN", "symbol": "GEN", "decimals": 18}, "rpc": ["https://eu.mainnet.xixoio.com", "https://us.mainnet.xixoio.com", "https://asia.mainnet.xixoio.com"], "faucets": [], "esploratori": [], "infoURL": "https://www.xixoio.com/" }, { "nome": "Newton", "chainId": 1012, "shortName": "nuovo", "chain": "NEW", "network": "mainnet", "networkId": 1012, "nativeCurrency": {"name": "Newton", "symbol": "NEW", "decimals": 18}, "rpc": ["https://global.rpc.mainnet.newtonproject.org"], "faucets": [], "esploratori": [], "infoURL": "https://www.newtonproject.org/" }, { "name": "Web3Games Testnet", "chainId": 102, "shortName": "w3g", "chain": "Web3Games", "network": "testnet", "networkId": 102, "nativeCurrency": {"name": "Web3Games", "symbol": "W3G", "decimals": 18}, "rpc": ["https://substrate.org.cn"], "faucets": [], "esploratori": [], "infoURL": "https://web3games.org/" }, { "name": "Clover Testnet", "chainId": 1023, "shortName": "tclv", "chain": "Clover", "network": "clover testnet", "networkId": 1023, "nativeCurrency": {"name": "Clover", "symbol": "CLV", "decimals": 18}, "rpc": [], "faucets": [], "esploratori": [], "infoURL": "https://clover.finance" }, { "name": "Clover Mainnet", "chainId": 1024, "shortName": "clv", "chain": "Clover", "network": "clover mainnet", "networkId": 1024, "nativeCurrency": {"name": "Clover", "symbol": "CLV", "decimals": 18}, "rpc": ["https://rpc-ivy.clover.finance", "https://rpc-ivy-2.clover.finance", "https://rpc-ivy-3.clover.finance" ], "faucets": [], "esploratori": [], "infoURL": "https://clover.finance" }, { "name": "ThunderCore Mainnet", "chainId": 108, "shortName": "TT", "chain": "TT", "network": "mainnet", "networkId": 108, "nativeCurrency": {"name": "ThunderCore Mainnet Ether", "symbol": "TT", "decimals": 18}, "rpc": ["https://mainnet-rpc.thundercore.com"], "faucets": ["https://faucet.thundercore.com"], "esploratori": [], "infoURL": "https://thundercore.com" }, { "name": "Metadium Mainnet", "chainId": 11, "shortName": "meta", "catena": "META", "network": "mainnet", "networkId": 11, "nativeCurrency": {"name": "Metadium Mainnet Ether", "symbol": "META", "decimals": 18}, "rpc": ["https://api.metadium.com/prod"], "faucets": [], "esploratori": [], "infoURL": "https://metadium.com" }, { "nome": "Rete IPOS", "chainId": 1122334455, "shortName": "ipos", "chain": "IPOS", "network": "mainnet", "networkId": 1122334455, "nativeCurrency": {"name": "IPOS Network Ether", "symbol": "IPOS", "decimals": 18}, "rpc": ["https://rpc.iposlab.com", "https://rpc2.iposlab.com"], "faucets": [], "esploratori": [], "infoURL": "https://iposlab.com" }, { "name": "MathChain", "chainId": 1139, "shortName": "MATH", "chain": "MATH", "network": "mainnet", "networkId": 1139, "nativeCurrency": {"name": "MathChain", "symbol": "MATH", "decimals": 18}, "rpc": [], "faucets": [], "esploratori": [], "infoURL": "https://mathchain.org" }, { "name": "MathChain Testnet", "chainId": 1140, "shortName": "tMATH", "chain": "MATH", "network": "testnet", "networkId": 1140, "nativeCurrency": {"name": "MathChain", "symbol": "MATH", "decimals": 18}, "rpc": ["https://galois-hk.maiziqianbao.net/rpc"], "faucets": ["https://scan.boka.network/#/Galois/faucet"], "esploratori": [], "infoURL": "https://mathchain.org" }, { "nome": "Metadium Testnet", "chainId": 12, "shortName": "kal", "catena": "META", "network": "testnet", "networkId": 12, "nativeCurrency": {"name": "Metadium Testnet Ether", "symbol": "KAL", "decimals": 18}, "rpc": ["https://api.metadium.com/dev"], "faucets": [], "esploratori": [], "infoURL": "https://metadium.com" }, { "name": "Fuse Mainnet", "chainId": 122, "shortName": "fusibile", "chain": "FUSE", "network": "mainnet", "networkId": 122, "nativeCurrency": {"name": "Fuse", "symbol": "FUSE", "decimals": 18}, "rpc": ["https://rpc.fuse.io"], "faucets": [], "esploratori": [], "infoURL": "https://fuse.io/" }, { "name": "Mainnet della catena Huobi ECO", "chainId": 128, "shortName": "heco", "chain": "Heco", "network": "mainnet", "networkId": 128, "nativeCurrency": {"name": "Huobi ECO Chain Native Token", "symbol": "HT", "decimals": 18}, "rpc": ["https://http-mainnet.hecochain.com", "wss: //ws-mainnet.hecochain.com"], "faucets": [], "esploratori": [], "infoURL": "https://hecoinfo.com" }, { "name": "Moonbeam Polkadot", "chainId": 1284, "shortName": "mbeam", "chain": "MOON", "rete": "raggio di luna", "networkId": 1284, "nativeCurrency": {"name": "Glimmer", "symbol": "GLMR", "decimals": 18}, "rpc": [], "faucets": [], "esploratori": [], "infoURL": "https://moonbeam.network/networks/moonbeam/" }, { "name": "Moonriver Kusama", "chainId": 1285, "shortName": "mriver", "chain": "MOON", "network": "moonriver", "networkId": 1285, "nativeCurrency": {"name": "River", "symbol": "RIVER", "decimals": 18}, "rpc": [], "faucets": [], "esploratori": [], "infoURL": "https://moonbeam.network/networks/moonriver/" }, { "name": "Moonrock Rococo", "chainId": 1286, "shortName": "mrock", "chain": "MOON", "network": "moonrock", "networkId": 1286, "nativeCurrency": {"name": "Rocs", "symbol": "ROC", "decimals": 18}, "rpc": [], "faucets": [], "esploratori": [], "infoURL": "" }, { "name": "Moonbeam Testnet Moonbase Alpha", "chainId": 1287, "shortName": "mbase", "chain": "MOON", "network": "moonbase", "networkId": 1287, "nativeCurrency": {"name": "Dev", "symbol": "DEV", "decimals": 18}, "rpc": ["https://rpc.testnet.moonbeam.network", "wss: //wss.testnet.moonbeam.network"], "faucets": [], "esploratori": [], "infoURL": "https://docs.moonbeam.network/networks/testnet/" }, { "name": "Diode Testnet Staging", "chainId": 13, "shortName": "dstg", "chain": "DIODE", "network": "testnet", "networkId": 13, "nativeCurrency": {"name": "Staging Diodes", "symbol": "sDIODE", "decimals": 18}, "rpc": ["https://staging.diode.io:8443/","wss://staging.diode.io:8443/ws"], "faucets": [], "esploratori": [], "infoURL": "https://diode.io/staging" }, { "nome": "Ether-1", "chainId": 1313114, "shortName": "etho", "chain": "ETHO", "network": "mainnet", "networkId": 1313114, "nativeCurrency": {"name": "Ether-1 Ether", "symbol": "ETHO", "decimals": 18}, "rpc": ["https://rpc.ether1.org"], "faucets": [], "esploratori": [], "infoURL": "https://ether1.org" }, { "name": "Aurora MainNet", "chainId": 1313161554, "shortName": "aurora", "chain": "NEAR", "network": "mainnet", "networkId": 1313161554, "nativeCurrency": {"name": "Ether", "symbol": "aETH", "decimals": 18}, "rpc": ["https://rpc.mainnet.aurora.dev:8545"], "faucets": [], "esploratori": [], "infoURL": "https://aurora.dev" }, { "name": "Aurora TestNet", "chainId": 1313161555, "shortName": "aurora-testnet", "chain": "NEAR", "network": "testnet", "networkId": 1313161555, "nativeCurrency": {"name": "Ether", "symbol": "aETH", "decimals": 18}, "rpc": ["https://rpc.testnet.aurora.dev:8545"], "faucets": [], "esploratori": [], "infoURL": "https://aurora.dev" }, { "nome": "Aurora BetaNet", "chainId": 1313161556, "shortName": "aurora-betanet", "chain": "NEAR", "network": "betanet", "networkId": 1313161556, "nativeCurrency": {"name": "Ether", "symbol": "aETH", "decimals": 18}, "rpc": ["https://rpc.betanet.aurora.dev:8545"], "faucets": [], "esploratori": [], "infoURL": "https://aurora.dev" }, { "nome": "Xerom", "chainId": 1313500, "shortName": "xero", "chain": "XERO", "network": "mainnet", "networkId": 1313500, "nativeCurrency": {"name": "Xerom Ether", "symbol": "XERO", "decimals": 18}, "rpc": ["https://rpc.xerom.org"], "faucets": [], "esploratori": [], "infoURL": "https://xerom.org" }, { "name": "PepChain Churchill", "chainId": 13371337, "shortName": "tpep", "chain": "PEP", "network": "testnet", "networkId": 13371337, "nativeCurrency": {"name": "PepChain Churchill Ether", "symbol": "TPEP", "decimals": 18}, "rpc": ["https://churchill-rpc.pepchain.io"], "faucets": [], "esploratori": [], "infoURL": "https://pepchain.io" }, { "name": "Matic Mainnet", "chainId": 137, "shortName": "matic", "chain": "Matic", "network": "mainnet", "networkId": 137, "nativeCurrency": {"name": "Matic", "symbol": "MATIC", "decimals": 18}, "rpc": ["https://rpc-mainnet.matic.network", "wss: //ws-mainnet.matic.network"], "faucets": [], "esploratori": [], "infoURL": "https://matic.network/" }, { "name": "Flare Mainnet", "chainId": 14, "shortName": "flr", "chain": "FLR", "network": "flare", "networkId": 14, "nativeCurrency": {"name": "Spark", "symbol": "FLR", "decimals": 18}, "rpc": [], "faucets": [], "esploratori": [], "infoURL": "https://flare.xyz" }, { "name": "Diode Prenet", "chainId": 15, "shortName": "diode", "chain": "DIODE", "network": "mainnet", "networkId": 15, "nativeCurrency": {"name": "Diodes", "symbol": "DIODE", "decimals": 18}, "rpc": ["https://prenet.diode.io:8443/","wss://prenet.diode.io:8443/ws"], "faucets": [], "esploratori": [], "infoURL": "https://diode.io/prenet" }, { "name": "Flare Testnet Coston", "chainId": 16, "shortName": "cflr", "chain": "FLR", "network": "coston", "networkId": 16, "nativeCurrency": {"name": "Coston Spark", "symbol": "CFLR", "decimals": 18}, "rpc": [], "faucets": ["https://faucet.towolabs.com"], "esploratori": [], "infoURL": "https://github.com/flare-eng/coston" }, { "name": "Lightstreams Testnet", "chainId": 162, "shortName": "tpht", "chain": "PHT", "network": "sirius", "networkId": 162, "nativeCurrency": {"name": "Lightstreams PHT", "symbol": "PHT", "decimals": 18}, "rpc": ["https://node.sirius.lightstreams.io"], "faucets": ["https://discuss.lightstreams.network/t/request-test-tokens"], "esploratori": [], "infoURL": "https://explorer.sirius.lightstreams.io" }, { "name": "Atheios", "chainId": 1620, "shortName": "ath", "chain": "ATH", "network": "mainnet", "networkId": 11235813, "nativeCurrency": {"name": "Atheios Ether", "symbol": "ATH", "decimals": 18}, "rpc": ["https://wallet.atheios.com:8797"], "faucets": [], "esploratori": [], "infoURL": "https://atheios.com" }, { "name": "Lightstreams Mainnet", "chainId": 163, "shortName": "pht", "chain": "PHT", "network": "mainnet", "networkId": 163, "nativeCurrency": {"name": "Lightstreams PHT", "symbol": "PHT", "decimals": 18}, "rpc": ["https://node.mainnet.lightstreams.io"], "faucets": [], "esploratori": [], "infoURL": "https://explorer.lightstreams.io" }, { "name": "Harmony Mainnet Shard 0", "chainId": 1666600000, "shortName": "hmy-s0", "chain": "Harmony", "network": "mainnet", "networkId": 1666600000, "nativeCurrency": {"name": "ONE", "symbol": "ONE", "decimals": 18}, "rpc": ["https://api.harmony.one"], "faucets": [], "esploratori": [], "infoURL": "https://www.harmony.one/" }, { "name": "Harmony Mainnet Shard 1", "chainId": 1666600001, "shortName": "hmy-s1", "chain": "Harmony", "network": "mainnet", "networkId": 1666600001, "nativeCurrency": {"name": "ONE", "symbol": "ONE", "decimals": 18}, "rpc": ["https://s1.api.harmony.one"], "faucets": [], "esploratori": [], "infoURL": "https://www.harmony.one/" }, { "name": "Harmony Mainnet Shard 2", "chainId": 1666600002, "shortName": "hmy-s2", "chain": "Harmony", "network": "mainnet", "networkId": 1666600002, "nativeCurrency": {"name": "ONE", "symbol": "ONE", "decimals": 18}, "rpc": ["https://s2.api.harmony.one"], "faucets": [], "esploratori": [], "infoURL": "https://www.harmony.one/" }, { "name": "Harmony Mainnet Shard 3", "chainId": 1666600003, "shortName": "hmy-s3", "chain": "Harmony", "network": "mainnet", "networkId": 1666600003, "nativeCurrency": {"name": "ONE", "symbol": "ONE", "decimals": 18}, "rpc": ["https://s3.api.harmony.one"], "faucets": [], "esploratori": [], "infoURL": "https://www.harmony.one/" }, { "name": "Harmony Testnet Shard 0", "chainId": 1666700000, "shortName": "hmy-b-s0", "chain": "Harmony", "network": "testnet", "networkId": 1666700000, "nativeCurrency": {"name": "ONE", "symbol": "ONE", "decimals": 18}, "rpc": ["https://api.s0.b.hmny.io"], "faucets": [], "esploratori": [], "infoURL": "https://www.harmony.one/" }, { "name": "Harmony Testnet Shard 1", "chainId": 1666700001, "shortName": "hmy-b-s1", "chain": "Harmony", "network": "testnet", "networkId": 1666700001, "nativeCurrency": {"name": "ONE", "symbol": "ONE", "decimals": 18}, "rpc": ["https://api.s1.b.hmny.io"], "faucets": [], "esploratori": [], "infoURL": "https://www.harmony.one/" }, { "name": "Harmony Testnet Shard 2", "chainId": 1666700002, "shortName": "hmy-b-s2", "chain": "Harmony", "network": "testnet", "networkId": 1666700002, "nativeCurrency": {"name": "ONE", "symbol": "ONE", "decimals": 18}, "rpc": ["https://api.s2.b.hmny.io"], "faucets": [], "esploratori": [], "infoURL": "https://www.harmony.one/" }, { "name": "Harmony Testnet Shard 3", "chainId": 1666700003, "shortName": "hmy-b-s3", "chain": "Harmony", "network": "testnet", "networkId": 1666700003, "nativeCurrency": {"name": "ONE", "symbol": "ONE", "decimals": 18}, "rpc": ["https://api.s3.b.hmny.io"], "faucets": [], "esploratori": [], "infoURL": "https://www.harmony.one/" }, { "name": "ThaiChain 2.0 ThaiFi", "chainId": 17, "shortName": "tfi", "chain": "TCH", "network": "thaifi", "networkId": 17, "nativeCurrency": {"name": "Thaifi Ether", "symbol": "TFI", "decimals": 18}, "rpc": ["https://rpc.thaifi.com"], "faucets": [], "esploratori": [], "infoURL": "https://exp.thaifi.com" }, { "name": "HOO Smart Chain Testnet", "chainId": 170, "shortName": "hoosmartchain", "chain": "ETH", "network": "testnet", "networkId": 170, "nativeCurrency": {"name": "HOO", "symbol": "HOO", "decimals": 18}, "rpc": ["https://http-testnet.hoosmartchain.com"], "faucets": ["https://faucet-testnet.hscscan.com/"], "esploratori": [], "infoURL": "https://www.hoosmartchain.com" }, { "name": "ThunderCore Testnet", "chainId": 18, "shortName": "TST", "chain": "TST", "network": "testnet", "networkId": 18, "nativeCurrency": {"name": "ThunderCore Testnet Ether", "symbol": "TST", "decimals": 18}, "rpc": ["https://testnet-rpc.thundercore.com"], "faucets": ["https://faucet-testnet.thundercore.com"], "esploratori": [], "infoURL": "https://thundercore.com" }, { "nome": "IOLite", "chainId": 18289463, "shortName": "ilt", "chain": "ILT", "network": "mainnet", "networkId": 18289463, "nativeCurrency": {"name": "IOLite Ether", "symbol": "ILT", "decimals": 18}, "rpc": ["https://net.iolite.io"], "faucets": [], "esploratori": [], "infoURL": "https://iolite.io" }, { "name": "Teslafunds", "chainId": 1856, "shortName": "tsf", "catena": "TSF", "network": "mainnet", "networkId": 1, "nativeCurrency": {"name": "Teslafunds Ether", "symbol": "TSF", "decimals": 18}, "rpc": ["https://tsfapi.europool.me"], "faucets": [], "esploratori": [], "infoURL": "https://teslafunds.io" }, { "name": "EtherGem", "chainId": 1987, "shortName": "egem", "chain": "EGEM", "network": "mainnet", "networkId": 1987, "nativeCurrency": {"name": "EtherGem Ether", "symbol": "EGEM", "decimals": 18}, "rpc": ["https://jsonrpc.egem.io/custom"], "faucets": [], "esploratori": [], "infoURL": "https://egem.io" }, { "name": "Expanse Network", "chainId": 2, "shortName": "exp", "chain": "EXP", "network": "mainnet", "networkId": 1, "nativeCurrency": {"name": "Expanse Network Ether", "symbol": "EXP", "decimals": 18}, "rpc": ["https://node.expanse.tech"], "faucets": [], "esploratori": [], "infoURL": "https://expanse.tech" }, { "name": "ELA-ETH-Sidechain Mainnet", "chainId": 20, "shortName": "elaeth", "chain": "ETH", "network": "mainnet", "networkId": 20, "nativeCurrency": {"name": "Elastos", "symbol": "ELA", "decimals": 18}, "rpc": ["https://mainrpc.elaeth.io"], "faucets": [], "esploratori": [], "infoURL": "https://www.elastos.org/" }, { "name": "Akroma", "chainId": 200625, "shortName": "aka", "chain": "AKA", "network": "mainnet", "networkId": 200625, "nativeCurrency": {"name": "Akroma Ether", "symbol": "AKA", "decimals": 18}, "rpc": ["https://remote.akroma.io"], "faucets": [], "esploratori": [], "infoURL": "https://akroma.io" }, { "name": "quarkblockchain", "chainId": 20181205, "shortName": "qki", "chain": "QKI", "network": "mainnet", "networkId": 20181205, "nativeCurrency": {"name": "quarkblockchain Native Token", "symbol": "QKI", "decimals": 18}, "rpc": ["https://hz.rpc.qkiscan.cn", "https://jp.rpc.qkiscan.io"], "faucets": [], "esploratori": [], "infoURL": "https://quarkblockchain.org/" }, { "name": "420coin", "chainId": 2020, "shortName": "420", "catena": "420", "network": "mainnet", "networkId": 2020, "nativeCurrency": {"name": "Fourtwenty", "symbol": "420", "decimals": 18}, "rpc": [], "faucets": [], "esploratori": [], "infoURL": "https://420integrated.com" }, { "nome": "Edgeware Mainnet", "chainId": 2021, "shortName": "edg", "chain": "EDG", "network": "mainnet", "networkId": 2021, "nativeCurrency": {"name": "Edge", "symbol": "EDG", "decimals": 18}, "rpc": ["https://mainnet1.edgewa.re"], "faucets": [], "esploratori": [], "infoURL": "http://edgewa.re" }, { "nome": "Beresheet Testnet", "chainId": 2022, "shortName": "edgt", "chain": "EDG", "network": "beresheet", "networkId": 2022, "nativeCurrency": {"name": "Testnet Edge", "symbol": "tEDG", "decimals": 18}, "rpc": ["https://beresheet1.edgewa.re"], "faucets": [], "esploratori": [], "infoURL": "http://edgewa.re" }, { "name": "ELA-ETH-Sidechain Testnet", "chainId": 21, "shortName": "elaetht", "chain": "ETH", "network": "testnet", "networkId": 21, "nativeCurrency": {"name": "Elastos", "symbol": "tELA", "decimals": 18}, "rpc": ["https://rpc.elaeth.io"], "faucets": ["https://faucet.elaeth.io/"], "esploratori": [], "infoURL": "https://elaeth.io/" }, { "name": "Freight Trust Network", "chainId": 211, "shortName": "EDI", "chain": "EDI", "network": "rete di trasporto merci e commercio", "networkId": 0, "nativeCurrency": {"name": "Freight Trust Native", "symbol": "0xF", "decimals": 18}, "rpc": ["http://13.57.207.168:3435","https://app.freighttrust.net/ftn/${API_KEY}"], "faucets": ["http://faucet.freight.sh"], "esploratori": [], "infoURL": "https://freighttrust.com" }, { "name": "ELA-DID-Sidechain Mainnet", "chainId": 22, "shortName": "eladid", "chain": "ETH", "network": "mainnet", "networkId": 22, "nativeCurrency": {"name": "Elastos", "symbol": "ELA", "decimals": 18}, "rpc": [], "faucets": [], "esploratori": [], "infoURL": "https://www.elastos.org/" }, { "name": "ELA-DID-Sidechain Testnet", "chainId": 23, "shortName": "eladidt", "chain": "ETH", "network": "testnet", "networkId": 23, "nativeCurrency": {"name": "Elastos", "symbol": "tELA", "decimals": 18}, "rpc": [], "faucets": [], "esploratori": [], "infoURL": "https://elaeth.io/" }, { "name": "Webchain", "chainId": 24484, "shortName": "web", "chain": "WEB", "network": "mainnet", "networkId": 37129, "nativeCurrency": {"name": "Webchain Ether", "symbol": "WEB", "decimals": 18}, "rpc": ["https://node1.webchain.network"], "faucets": [], "esploratori": [], "infoURL": "https://webchain.network" }, { "name": "Energy Web Chain", "chainId": 246, "shortName": "ewt", "chain": "Energy Web Chain", "network": "mainnet", "networkId": 246, "nativeCurrency": {"name": "Energy Web Token", "symbol": "EWT", "decimals": 18}, "rpc": ["https://rpc.energyweb.org", "wss: //rpc.energyweb.org/ws"], "faucets": ["https://faucet.carbonswap.exchange"], "esploratori": [], "infoURL": "https://energyweb.org" }, { "nome": "ARTIS sigma1", "chainId": 246529, "shortName": "ats", "catena": "ARTIS", "rete": "sigma1", "networkId": 246529, "nativeCurrency": {"name": "ARTIS sigma1 Ether", "symbol": "ATS", "decimals": 18}, "rpc": ["https://rpc.sigma1.artis.network"], "faucets": [], "esploratori": [], "infoURL": "https://artis.eco" }, { "name": "ARTIS Testnet tau1", "chainId": 246785, "shortName": "atstau", "catena": "ARTIS", "network": "tau1", "networkId": 246785, "nativeCurrency": {"name": "ARTIS tau1 Ether", "symbol": "tATS", "decimals": 18}, "rpc": ["https://rpc.tau1.artis.network"], "faucets": [], "esploratori": [], "infoURL": "https://artis.network" }, { "name": "MintMe.com Coin", "chainId": 24734, "shortName": "mintme", "catena": "MINTME", "network": "mainnet", "networkId": 37480, "nativeCurrency": {"name": "MintMe.com Coin", "symbol": "MINTME", "decimals": 18}, "rpc": ["https://node1.mintme.com"], "faucets": [], "esploratori": [], "infoURL": "https://www.mintme.com" }, { "name": "Fantom Opera", "chainId": 250, "shortName": "ftm", "catena": "FTM", "network": "mainnet", "networkId": 250, "nativeCurrency": {"name": "Fantom", "symbol": "FTM", "decimals": 18}, "rpc": ["https://rpcapi.fantom.network"], "faucets": [], "explorers": [{"name": "ftmscan", "url": "https://ftmscan.com", "icon": "ftmscan", "standard": "EIP3091"}], "infoURL": "https://fantom.foundation" }, { "name": "Huobi ECO Chain Testnet", "chainId": 256, "shortName": "hecot", "chain": "Heco", "network": "testnet", "networkId": 256, "nativeCurrency": {"name": "Huobi ECO Chain Test Native Token", "symbol": "ht", "decimals": 18}, "rpc": ["https://http-testnet.hecochain.com", "wss: //ws-testnet.hecochain.com"], "faucets": ["https://scan-testnet.hecochain.com/faucet"], "esploratori": [], "infoURL": "https://testnet.hecoinfo.com" }, { "name": "Blockchain ad alte prestazioni", "chainId": 269, "shortName": "hpb", "chain": "HPB", "network": "mainnet", "networkId": 100, "nativeCurrency": {"name": "High Performance Blockchain Ether", "symbol": "HPB", "decimals": 18}, "rpc": ["https://hpb.app"], "faucets": [], "esploratori": [], "infoURL": "https://hpbscan.org/" }, { "name": "Auxilium Network Mainnet", "chainId": 28945486, "shortName": "auxi", "chain": "AUX", "network": "mainnet", "networkId": 28945486, "nativeCurrency": {"name": "Auxilium coin", "symbol": "AUX", "decimals": 18}, "rpc": ["https://rpc.auxilium.global"], "faucets": [], "esploratori": [], "infoURL": "https://auxilium.global" }, { "name": "Ethereum Testnet Ropsten", "chainId": 3, "shortName": "rop", "chain": "ETH", "network": "ropsten", "networkId": 3, "nativeCurrency": {"name": "Ropsten Ether", "symbol": "ROP", "decimals": 18}, "rpc": ["https://ropsten.infura.io/v3/${INFURA_API_KEY}","wss://ropsten.infura.io/ws/v3/${INFURA_API_KEY}"], "faucets": ["https://faucet.ropsten.be?${ADDRESS}"], "esploratori": [], "infoURL": "https://github.com/ethereum/ropsten" }, { "name": "RSK Mainnet", "chainId": 30, "shortName": "rsk", "chain": "RSK", "network": "mainnet", "networkId": 30, "nativeCurrency": {"name": "RSK Mainnet Ether", "symbol": "RBTC", "decimals": 18}, "rpc": ["https://public-node.rsk.co", "https://mycrypto.rsk.co"], "faucets": [], "esploratori": [], "infoURL": "https://rsk.co" }, { "nome": "RSK Testnet", "chainId": 31, "shortName": "trsk", "chain": "RSK", "network": "testnet", "networkId": 31, "nativeCurrency": {"name": "RSK Testnet Ether", "symbol": "tRBTC", "decimals": 18}, "rpc": ["https://public-node.testnet.rsk.co", "https://mycrypto.testnet.rsk.co"], "faucets": ["https://faucet.testnet.rsk.co"], "esploratori": [], "infoURL": "https://rsk.co" }, { "name": "Ethersocial Network", "chainId": 31102, "shortName": "esn", "chain": "ESN", "network": "mainnet", "networkId": 1, "nativeCurrency": {"name": "Ethersocial Network Ether", "symbol": "ESN", "decimals": 18}, "rpc": ["https://api.esn.gonspool.com"], "faucets": [], "esploratori": [], "infoURL": "https://ethersocial.org" }, { "name": "Pirl", "chainId": 3125659152, "shortName": "pirl", "chain": "PIRL", "network": "mainnet", "networkId": 3125659152, "nativeCurrency": {"name": "Pirl Ether", "symbol": "PIRL", "decimals": 18}, "rpc": ["https://wallrpc.pirl.io"], "faucets": [], "esploratori": [], "infoURL": "https://pirl.io" }, { "name": "KuCoin Community Chain Testnet", "chainId": 322, "shortName": "kcc", "chain": "KCC", "network": "testnet", "networkId": 322, "nativeCurrency": {"name": "KuCoin Testnet Token", "symbol": "KCS", "decimals": 18}, "rpc": ["https://rpc-testnet.kcc.network"], "faucets": ["https://faucet-testnet.kcc.network"], "explorers": [{"name": "kcc-scan", "url": "https://scan-testnet.kcc.network", "standard": "EIP3091"}], "infoURL": "https://scan-testnet.kcc.network" }, { "name": "Fusion Mainnet", "chainId": 32659, "shortName": "fsn", "chain": "FSN", "network": "mainnet", "networkId": 32659, "nativeCurrency": {"name": "Fusion", "symbol": "FSN", "decimals": 18}, "rpc": ["https://mainnet.anyswap.exchange", "https://fsn.dev/api"], "faucets": [], "esploratori": [], "infoURL": "https://www.fusion.org/" }, { "name": "GoodData Mainnet", "chainId": 33, "shortName": "GooD", "chain": "GooD", "network": "mainnet", "networkId": 33, "nativeCurrency": {"name": "GoodData Mainnet Ether", "symbol": "GooD", "decimals": 18}, "rpc": ["https://rpc.goodata.io"], "faucets": [], "esploratori": [], "infoURL": "https://www.goodata.org" }, { "nome": "Catena TBWG", "chainId": 35, "shortName": "tbwg", "chain": "TBWG", "network": "mainnet", "networkId": 35, "nativeCurrency": {"name": "TBWG Ether", "symbol": "TBG", "decimals": 18}, "rpc": ["https://rpc.tbwg.io"], "faucets": [], "esploratori": [], "infoURL": "https://tbwg.io" }, { "name": "Joys Digital Mainnet", "chainId": 35855456, "shortName": "JOYS", "chain": "JOYS", "network": "mainnet", "networkId": 35855456, "nativeCurrency": {"name": "JOYS", "symbol": "JOYS", "decimals": 18}, "rpc": ["https://node.joys.digital"], "faucets": [], "esploratori": [], "infoURL": "https://joys.digital" }, { "nome": "Valorbit", "chainId": 38, "shortName": "val", "catena": "VAL", "network": "mainnet", "networkId": 38, "nativeCurrency": {"name": "Valorbit", "symbol": "VAL", "decimals": 18}, "rpc": ["https://rpc.valorbit.com/v2"], "faucets": [], "esploratori": [], "infoURL": "https://valorbit.com" }, { "name": "Lisinski", "chainId": 385, "shortName": "lisinski", "catena": "CRO", "network": "mainnet", "networkId": 385, "nativeCurrency": {"name": "Lisinski Ether", "symbol": "LISINSKI", "decimals": 18}, "rpc": ["https://rpc-bitfalls1.lisinski.online"], "faucets": ["https://pipa.lisinski.online"], "esploratori": [], "infoURL": "https://lisinski.online" }, { "name": "Energi Mainnet", "chainId": 39797, "shortName": "nrg", "chain": "NRG", "network": "mainnet", "networkId": 39797, "nativeCurrency": {"name": "Energi", "symbol": "NRG", "decimals": 18}, "rpc": ["https://nodeapi.gen3.energi.network"], "faucets": [], "esploratori": [], "infoURL": "https://www.energi.world/" }, { "name": "Ethereum Testnet Rinkeby", "chainId": 4, "shortName": "rin", "chain": "ETH", "network": "rinkeby", "networkId": 4, "nativeCurrency": {"name": "Rinkeby Ether", "symbol": "RIN", "decimals": 18}, "rpc": ["https://rinkeby.infura.io/v3/${INFURA_API_KEY}","wss://rinkeby.infura.io/ws/v3/${INFURA_API_KEY}"], "faucets": ["https://faucet.rinkeby.io"], "esploratori": [], "infoURL": "https://www.rinkeby.io" }, { "nome": "Telos EVM Mainnet", "chainId": 40, "shortName": "Telos EVM", "chain": "TLOS", "network": "mainnet", "networkId": 40, "nativeCurrency": {"name": "Telos", "symbol": "TLOS", "decimals": 18}, "rpc": ["https://mainnet.telos.net/evm"], "faucets": [], "esploratori": [], "infoURL": "https://telos.net" }, { "nome": "Telos EVM Testnet", "chainId": 41, "shortName": "Telos EVM Testnet", "chain": "TLOS", "network": "testnet", "networkId": 41, "nativeCurrency": {"name": "Telos", "symbol": "TLOS", "decimals": 18}, "rpc": ["https://testnet.telos.net/evm"], "faucets": ["https://app.telos.net/testnet/developers"], "esploratori": [], "infoURL": "https://telos.net" }, { "name": "Ethereum Testnet Kovan", "chainId": 42, "shortName": "kov", "chain": "ETH", "rete": "kovan", "networkId": 42, "nativeCurrency": {"name": "Kovan Ether", "symbol": "KOV", "decimals": 18}, "rpc": ["https://kovan.poa.network", "http://kovan.poa.network:8545", "https://kovan.infura.io/v3/${INFURA_API_KEY}", "wss: //kovan.infura.io/ws/v3/$ {INFURA_API_KEY}", "ws: //kovan.poa.network: 8546"], "faucets": ["https://faucet.kovan.network", "https://gitter.im/kovan-testnet/faucet"], "esploratori": [], "infoURL": "https://kovan-testnet.github.io/website" }, { "name": "Optimistic Ethereum Testnet Goerli", "chainId": 420, "shortName": "ogor", "chain": "ETH", "network": "goerli", "networkId": 420, "nativeCurrency": {"name": "Görli Ether", "symbol": "GOR", "decimals": 18}, "rpc": ["https://goerli.optimism.io/"], "faucets": [], "esploratori": [], "infoURL": "https://optimism.io" }, { "name": "pegglecoin", "chainId": 42069, "shortName": "PC", "catena": "42069", "network": "mainnet", "networkId": 42069, "nativeCurrency": {"name": "pegglecoin", "symbol": "peggle", "decimals": 18}, "rpc": [], "faucets": [], "esploratori": [], "infoURL": "https://teampeggle.com" }, { "name": "Celo Mainnet", "chainId": 42220, "shortName": "CELO", "chain": "CELO", "network": "Mainnet", "networkId": 42220, "nativeCurrency": {"name": "CELO", "symbol": "CELO", "decimals": 18}, "rpc": ["https://forno.celo.org", "wss: //forno.celo.org/ws"], "faucets": [], "esploratori": [], "infoURL": "https://docs.celo.org/" }, { "name": "Testnet Darwinia Pangolin", "chainId": 43, "shortName": "darwinia", "chain": "pangolin", "network": "testnet gratuito", "networkId": 43, "nativeCurrency": {"name": "Pangolin RING", "symbol": "PRING", "decimals": 9}, "rpc": [], "faucets": [], "esploratori": [], "infoURL": "https://darwinia.network/" }, { "name": "Athereum", "chainId": 43110, "shortName": "avaeth", "chain": "ATH", "network": "athereum", "networkId": 43110, "nativeCurrency": {"name": "Athereum Ether", "symbol": "ATH", "decimals": 18}, "rpc": ["https://ava.network:21015/ext/evm/rpc"], "faucets": ["http://athfaucet.ava.network//?address=${ADDRESS}"], "esploratori": [], "infoURL": "https://athereum.ava.network" }, { "name": "Avalanche Fuji Testnet", "chainId": 43113, "shortName": "Fuji", "chain": "AVAX", "network": "testnet", "networkId": 1, "nativeCurrency": {"name": "Avalanche", "symbol": "AVAX", "decimals": 18}, "rpc": ["https://api.avax-test.network/ext/bc/C/rpc"], "faucets": ["https://faucet.avax-test.network/"], "esploratori": [], "infoURL": "https://cchain.explorer.avax-test.network" }, { "name": "Avalanche Mainnet", "chainId": 43114, "shortName": "Avalanche", "chain": "AVAX", "network": "mainnet", "networkId": 1, "nativeCurrency": {"name": "Avalanche", "symbol": "AVAX", "decimals": 18}, "rpc": ["https://api.avax.network/ext/bc/C/rpc"], "faucets": [], "esploratori": [], "infoURL": "https://cchain.explorer.avax.network/" }, { "name": "Darwinia Crab Network", "chainId": 44, "shortName": "crab", "chain": "crab", "network": "Crab network", "networkId": 44, "nativeCurrency": {"name": "Crab Token", "symbol": "CRING", "decimals": 9}, "rpc": [], "faucets": [], "esploratori": [], "infoURL": "https://crab.network/" }, { "name": "Celo Alfajores Testnet", "chainId": 44787, "shortName": "ALFA", "chain": "CELO", "network": "Alfajores", "networkId": 44787, "nativeCurrency": {"name": "CELO", "symbol": "CELO", "decimals": 18}, "rpc": ["https://alfajores-forno.celo-testnet.org", "wss: //alfajores-forno.celo-testnet.org/ws"], "faucets": ["https://celo.org/developers/faucet","https://cauldron.pretoriaresearchlab.io/alfajores-faucet"], "esploratori": [], "infoURL": "https://docs.celo.org/" }, { "name": "IoTeX Network Mainnet", "chainId": 4689, "shortName": "iotex-mainnet", "chain": "iotex.io", "network": "mainnet", "networkId": 4689, "nativeCurrency": {"name": "IoTeX", "symbol": "IOTX", "decimals": 18}, "rpc": ["https://babel-api.mainnet.iotex.io"], "faucets": [], "esploratori": [], "infoURL": "https://iotex.io" }, { "name": "IoTeX Network Testnet", "chainId": 4690, "shortName": "iotex-testnet", "chain": "iotex.io", "network": "testnet", "networkId": 4690, "nativeCurrency": {"name": "IoTeX", "symbol": "IOTX", "decimals": 18}, "rpc": ["https://babel-api.testnet.iotex.io"], "faucets": ["https://faucet.iotex.io/"], "esploratori": [], "infoURL": "https://iotex.io" }, { "nome": "Energi Testnet", "chainId": 49797, "shortName": "tnrg", "chain": "NRG", "network": "testnet", "networkId": 49797, "nativeCurrency": {"name": "Energi", "symbol": "tNRG", "decimals": 18}, "rpc": ["https://nodeapi.test3.energi.network"], "faucets": [], "esploratori": [], "infoURL": "https://www.energi.world/" }, { "nome": "Rupaya", "chainId": 499, "shortName": "rupx", "catena": "RUPX", "network": "mainnet", "networkId": 499, "nativeCurrency": {"name": "Rupaya", "symbol": "RUPX", "decimals": 18}, "rpc": [], "faucets": [], "esploratori": [], "infoURL": "https://www.rupx.io" }, { "name": "Ethereum Testnet Görli", "chainId": 5, "shortName": "gor", "chain": "ETH", "network": "goerli", "networkId": 5, "nativeCurrency": {"name": "Görli Ether", "symbol": "GOR", "decimals": 18}, "rpc": ["https://rpc.goerli.mudit.blog/","https://rpc.slock.it/goerli", "https://goerli.prylabs.net/"], "faucets": ["https://goerli-faucet.slock.it/?address=${ADDRESS}","https://faucet.goerli.mudit.blog"], "esploratori": [], "infoURL": "https://goerli.net/#about" }, { "name": "XinFin Network Mainnet", "chainId": 50, "shortName": "xdc", "catena": "XDC", "network": "mainnet", "networkId": 50, "nativeCurrency": {"name": "XinFin", "symbol": "XDC", "decimals": 18}, "rpc": ["https://rpc.xinfin.network"], "faucets": [], "esploratori": [], "infoURL": "https://xinfin.org" }, { "name": "XinFin Apothem Testnet", "chainId": 51, "shortName": "TXDC", "catena": "TXDC", "network": "testnet", "networkId": 51, "nativeCurrency": {"name": "XinFinTest", "symbol": "TXDC", "decimals": 18}, "rpc": ["https://rpc.apothem.network"], "faucets": [], "esploratori": [], "infoURL": "https://xinfin.org" }, { "name": "EraSwap Mainnet", "chainId": 5197, "shortName": "es", "chain": "ESN", "network": "mainnet", "networkId": 5197, "nativeCurrency": {"name": "EraSwap", "symbol": "ES", "decimals": 18}, "rpc": ["https://mainnet.eraswap.network", "https://rpc-mumbai.mainnet.eraswap.network"], "faucets": [], "esploratori": [], "infoURL": "https://eraswap.info/" }, { "name": "CoinEx Smart Chain Mainnet", "chainId": 52, "shortName": "cet", "catena": "CSC", "network": "mainnet", "networkId": 52, "nativeCurrency": {"name": "CoinEx Chain Native Token", "symbol": "cet", "decimals": 18}, "rpc": ["https://rpc-mainnet.coinex.net"], "faucets": [], "esploratori": [], "infoURL": "http://www.coinex.org/" }, { "name": "CoinEx Smart Chain Testnet", "chainId": 53, "shortName": "tcet", "catena": "CSC", "network": "testnet", "networkId": 53, "nativeCurrency": {"name": "CoinEx Chain Test Native Token", "symbol": "cett", "decimals": 18}, "rpc": ["https://rpc-testnet.coinex.net"], "faucets": [], "esploratori": [], "infoURL": "http://www.coinex.org/" }, { "name": "Tao Network", "chainId": 558, "shortName": "tao", "chain": "TAO", "network": "core", "networkId": 558, "nativeCurrency": {"name": "Tao", "symbol": "TAO", "decimals": 18}, "rpc": ["https://rpc.testnet.tao.network", "http://rpc.testnet.tao.network:8545", "https://rpc.tao.network", "wss: //rpc.tao.network "], "faucets": [], "esploratori": [], "infoURL": "https://tao.network" }, { "name": "Binance Smart Chain Mainnet", "chainId": 56, "shortName": "bnb", "chain": "BSC", "network": "mainnet", "networkId": 56, "nativeCurrency": {"name": "Binance Chain Native Token", "symbol": "BNB", "decimals": 18}, "rpc": ["https://bsc-dataseed1.binance.org", "https://bsc-dataseed2.binance.org", "https://bsc-dataseed3.binance.org", "https: //bsc-dataseed4.binance.org","https://bsc-dataseed1.defibit.io","https://bsc-dataseed2.defibit.io","https://bsc-dataseed3.defibit. io "," https://bsc-dataseed4.defibit.io "," https://bsc-dataseed1.ninicoin.io "," https://bsc-dataseed2.ninicoin.io "," https: // bsc-dataseed3.ninicoin.io "," https://bsc-dataseed4.ninicoin.io "," wss: //bsc-ws-node.nariox.org "], "faucets": [], "explorers": [{"name": "bscscan", "url": "https://bscscan.com", "standard": "EIP3091"}], "infoURL": "https://www.binance.org" }, { "name": "Mainnet Wegochain Rubidium", "chainId": 5869, "shortName": "rbd", "chain": "RBD", "network": "mainnet", "networkId": 5869, "nativeCurrency": {"name": "Rubid", "symbol": "RBD", "decimals": 18}, "rpc": ["https://proxy.wegochain.io", "http://wallet.wegochain.io:7764"], "faucets": [], "esploratori": [], "infoURL": "http://wegochain.io" }, { "name": "Acala Mandala Testnet", "chainId": 595, "shortName": "maca", "chain": "mACA", "network": "testnet", "networkId": 595, "nativeCurrency": {"name": "Acala Mandala Token", "symbol": "mACA", "decimals": 18}, "rpc": [], "faucets": [], "esploratori": [], "infoURL": "https://acala.network" }, { "name": "Ethereum Classic Testnet Kotti", "chainId": 6, "shortName": "kot", "chain": "ETC", "network": "kotti", "networkId": 6, "nativeCurrency": {"name": "Kotti Ether", "symbol": "KOT", "decimals": 18}, "rpc": [], "faucets": [], "esploratori": [], "infoURL": "https://explorer.jade.builders/?network=kotti" }, { "name": "GoChain", "chainId": 60, "shortName": "vai", "chain": "GO", "network": "mainnet", "networkId": 60, "nativeCurrency": {"name": "GoChain Ether", "symbol": "GO", "decimals": 18}, "rpc": ["https://rpc.gochain.io"], "faucets": [], "esploratori": [], "infoURL": "https://gochain.io" }, { "name": "Ethereum Classic Mainnet", "chainId": 61, "shortName": "ecc", "chain": "ETC", "network": "mainnet", "networkId": 1, "nativeCurrency": {"name": "Ethereum Classic Ether", "symbol": "ETC", "decimals": 18}, "rpc": ["https://ethereumclassic.network"], "faucets": [], "esploratori": [], "infoURL": "https://ethereumclassic.org" }, { "name": "Aquachain", "chainId": 61717561, "shortName": "aqua", "chain": "AQUA", "network": "mainnet", "networkId": 61717561, "nativeCurrency": {"name": "Aquachain Ether", "symbol": "AQUA", "decimals": 18}, "rpc": ["https://c.onical.org", "https://tx.aquacha.in/api"], "faucets": ["https://aquacha.in/faucet"], "esploratori": [], "infoURL": "https://aquachain.github.io" }, { "name": "Ethereum Classic Testnet Morden", "chainId": 62, "shortName": "tetc", "chain": "ETC", "network": "testnet", "networkId": 2, "nativeCurrency": {"name": "Ethereum Classic Testnet Ether", "symbol": "TETC", "decimals": 18}, "rpc": [], "faucets": [], "esploratori": [], "infoURL": "https://ethereumclassic.org" }, { "name": "Celo Baklava Testnet", "chainId": 62320, "shortName": "BKLV", "chain": "CELO", "rete": "Baklava", "networkId": 62320, "nativeCurrency": {"name": "CELO", "symbol": "CELO", "decimals": 18}, "rpc": ["https://baklava-forno.celo-testnet.org"], "faucets": ["https://docs.google.com/forms/d/e/1FAIpQLSdfr1BwUTYepVmmvfVUDRCwALejZ-TUva2YujNpvrEmPAX2pg/viewform","https://cauldron.pretoriaresearchlab.io/baklava-faucet" "esploratori": [], "infoURL": "https://docs.celo.org/" }, { "name": "Ethereum Classic Testnet Mordor", "chainId": 63, "shortName": "metc", "chain": "ETC", "network": "testnet", "networkId": 7, "nativeCurrency": {"name": "Mordor Classic Testnet Ether", "symbol": "METC", "decimals": 18}, "rpc": [], "faucets": [], "esploratori": [], "infoURL": "https://github.com/eth-classic/mordor/" }, { "name": "Ellaism", "chainId": 64, "shortName": "ella", "catena": "ELLA", "network": "mainnet", "networkId": 64, "nativeCurrency": {"name": "Ellaism Ether", "symbol": "ELLA", "decimals": 18}, "rpc": ["https://jsonrpc.ellaism.org"], "faucets": [], "esploratori": [], "infoURL": "https://ellaism.org" }, { "nome": "OKExChain Testnet", "chainId": 65, "shortName": "tokt", "chain": "okexchain", "network": "testnet", "networkId": 65, "nativeCurrency": {"name": "OKExChain Global Utility Token in testnet", "symbol": "OKT", "decimals": 18}, "rpc": ["https://exchaintestrpc.okex.org"], "faucets": ["https://www.okex.com/drawdex"], "explorers": [{"name": "OKLink", "url": "https://www.oklink.com/okexchain-test", "standard": "EIP3091"}], "infoURL": "https://www.okex.com/okexchain" }, { "name": "OKExChain Mainnet", "chainId": 66, "shortName": "okt", "chain": "okexchain", "network": "mainnet", "networkId": 66, "nativeCurrency": {"name": "OKExChain Global Utility Token", "symbol": "OKT", "decimals": 18}, "rpc": ["https://exchainrpc.okex.org"], "faucets": [], "explorers": [{"name": "OKLink", "url": "https://www.oklink.com/okexchain", "standard": "EIP3091"}], "infoURL": "https://www.okex.com/okexchain" }, { "nome": "DBChain Testnet", "chainId": 67, "shortName": "dbm", "catena": "DBM", "network": "testnet", "networkId": 67, "nativeCurrency": {"name": "DBChain Testnet", "symbol": "DBM", "decimals": 18}, "rpc": ["http://test-rpc.dbmbp.com"], "faucets": [], "esploratori": [], "infoURL": "http://test.dbmbp.com" }, { "nome": "SoterOne Mainnet", "chainId": 68, "shortName": "SO1", "chain": "SOTER", "network": "mainnet", "networkId": 68, "nativeCurrency": {"name": "SoterOne Mainnet Ether", "symbol": "SOTER", "decimals": 18}, "rpc": ["https://rpc.soter.one"], "faucets": [], "esploratori": [], "infoURL": "https://www.soterone.com" }, { "name": "Karura Network", "chainId": 686, "shortName": "kar", "chain": "KAR", "network": "mainnet", "networkId": 686, "nativeCurrency": {"name": "Karura Token", "symbol": "KAR", "decimals": 18}, "rpc": [], "faucets": [], "esploratori": [], "infoURL": "https://karura.network" }, { "name": "Optimistic Ethereum Testnet Kovan", "chainId": 69, "shortName": "okov", "chain": "ETH", "rete": "kovan", "networkId": 69, "nativeCurrency": {"name": "Kovan Ether", "symbol": "KOR", "decimals": 18}, "rpc": ["https://kovan.optimism.io/"], "faucets": [], "esploratori": [], "infoURL": "https://optimism.io" }, { "name": "ThaiChain", "chainId": 7, "shortName": "tch", "chain": "TCH", "network": "mainnet", "networkId": 7, "nativeCurrency": {"name": "ThaiChain Ether", "symbol": "TCH", "decimals": 18}, "rpc": ["https://rpc.dome.cloud"], "faucets": [], "esploratori": [], "infoURL": "https://thaichain.io" }, { "nome": "Energy Web Volta Testnet", "chainId": 73799, "shortName": "vt", "chain": "Volta", "network": "testnet", "networkId": 73799, "nativeCurrency": {"name": "Volta Token", "symbol": "VT", "decimals": 18}, "rpc": ["https://volta-rpc.energyweb.org", "wss: //volta-rpc.energyweb.org/ws"], "faucets": ["https://voltafaucet.energyweb.org"], "esploratori": [], "infoURL": "https://energyweb.org" }, { "name": "Mix", "chainId": 76, "shortName": "mix", "chain": "MIX", "network": "mainnet", "networkId": 76, "nativeCurrency": {"name": "Mix Ether", "symbol": "MIX", "decimals": 18}, "rpc": ["https://rpc2.mix-blockchain.org:8647"], "faucets": [], "esploratori": [], "infoURL": "https://mix-blockchain.org" }, { "nome": "POA Network Sokol", "chainId": 77, "shortName": "poa", "chain": "POA", "network": "sokol", "networkId": 77, "nativeCurrency": {"name": "POA Sokol Ether", "symbol": "POA", "decimals": 18}, "rpc": ["https://sokol.poa.network", "wss: //sokol.poa.network/wss", "ws: //sokol.poa.network: 8546"], "faucets": ["https://faucet-sokol.herokuapp.com"], "esploratori": [], "infoURL": "https://poa.network" }, { "name": "Musicoin", "chainId": 7762959, "shortName": "music", "chain": "MUSIC", "network": "mainnet", "networkId": 7762959, "nativeCurrency": {"name": "Musicoin", "symbol": "MUSIC", "decimals": 18}, "rpc": ["https://mewapi.musicoin.tw"], "faucets": [], "esploratori": [], "infoURL": "https://musicoin.tw" }, { "nome": "Ethermint Testnet", "chainId": 777, "shortName": "emint", "catena": "ETHERMINT", "network": "testnet", "networkId": 777, "nativeCurrency": {"name": "Photon", "symbol": "Photon", "decimals": 18}, "rpc": ["http://54.210.246.165:8545"], "faucets": [], "esploratori": [], "infoURL": "https://docs.ethermint.zone" }, { "name": "Mainnet PrimusChain", "chainId": 78, "shortName": "primuschain", "chain": "PC", "network": "mainnet", "networkId": 78, "nativeCurrency": {"name": "Primus Ether", "symbol": "PETH", "decimals": 18}, "rpc": ["https://ethnode.primusmoney.com/mainnet"], "faucets": [], "esploratori": [], "infoURL": "https://primusmoney.com" }, { "name": "Firenze test network", "chainId": 78110, "shortName": "firenze", "chain": "ETH", "network": "testnet", "networkId": 78110, "nativeCurrency": {"name": "Firenze Ether", "symbol": "FIN", "decimals": 18}, "rpc": ["https://ethnode.primusmoney.com/firenze"], "faucets": [], "esploratori": [], "infoURL": "https://primusmoney.com" }, { "name": "Acala Network", "chainId": 787, "shortName": "aca", "chain": "ACA", "network": "mainnet", "networkId": 787, "nativeCurrency": {"name": "Acala Token", "symbol": "ACA", "decimals": 18}, "rpc": [], "faucets": [], "esploratori": [], "infoURL": "https://acala.network" }, { "name": "Ubiq Network Mainnet", "chainId": 8, "shortName": "ubq", "chain": "UBQ", "network": "mainnet", "networkId": 88, "nativeCurrency": {"name": "Ubiq Ether", "symbol": "UBQ", "decimals": 18}, "rpc": ["https://rpc.octano.dev", "https://pyrus2.ubiqscan.io"], "faucets": [], "esploratori": [], "infoURL": "https://ubiqsmart.com" }, { "name": "GeneChain", "chainId": 80, "shortName": "GeneChain", "chain": "GeneChain", "network": "mainnet", "networkId": 80, "nativeCurrency": {"name": "RNA", "symbol": "RNA", "decimals": 18}, "rpc": ["https://rpc.genechain.io"], "faucets": [], "explorers": [{"name": "GeneChain Scan", "url": "https://scan.genechain.io", "standard": "EIP3091"}], "infoURL": "https://scan.genechain.io/" }, { "name": "Matic Testnet Mumbai", "chainId": 80001, "shortName": "maticmum", "chain": "Matic", "network": "testnet", "networkId": 80001, "nativeCurrency": {"name": "Matic", "symbol": "tMATIC", "decimals": 18}, "rpc": ["https://rpc-mumbai.matic.today", "wss: //ws-mumbai.matic.today"], "faucets": ["https://faucet.matic.network/"], "esploratori": [], "infoURL": "https://matic.network/" }, { "nome": "MDGL Testnet", "chainId": 8029, "shortName": "mdgl", "chain": "MDGL", "network": "testnet", "networkId": 8029, "nativeCurrency": {"name": "MDGL Token", "symbol": "MDGLT", "decimals": 18}, "rpc": ["https://testnet.mdgl.io"], "faucets": [], "esploratori": [], "infoURL": "https://mdgl.io" }, { "name": "GeneChain Adenine Testnet", "chainId": 8080, "shortName": "GeneChainAdn", "chain": "GeneChain", "network": "adenine", "networkId": 8080, "nativeCurrency": {"name": "Testnet RNA", "symbol": "tRNA", "decimals": 18}, "rpc": ["https://rpc-testnet.genechain.io"], "faucets": ["https://faucet.genechain.io"], "explorers": [{"name": "GeneChain Adenine Testnet Scan", "url": "https://scan-testnet.genechain.io", "standard": "EIP3091"}], "infoURL": "https://scan-testnet.genechain.io/" }, { "name": "Meter Mainnet", "chainId": 82, "shortName": "Meter", "chain": "METER", "network": "mainnet", "networkId": 82, "nativeCurrency": {"name": "Meter", "symbol": "MTR", "decimals": 18}, "rpc": ["https://rpc.meter.io"], "faucets": [], "esploratori": [], "infoURL": "https://www.meter.io" }, { "name": "Callisto Mainnet", "chainId": 820, "shortName": "clo", "chain": "CLO", "network": "mainnet", "networkId": 1, "nativeCurrency": {"name": "Callisto Mainnet Ether", "symbol": "CLO", "decimals": 18}, "rpc": ["https://clo-geth.0xinfra.com"], "faucets": [], "esploratori": [], "infoURL": "https://callisto.network" }, { "name": "Callisto Testnet", "chainId": 821, "shortName": "tclo", "chain": "CLO", "network": "testnet", "networkId": 2, "nativeCurrency": {"name": "Callisto Testnet Ether", "symbol": "TCLO", "decimals": 18}, "rpc": [], "faucets": [], "esploratori": [], "infoURL": "https://callisto.network" }, { "nome": "Klaytn Mainnet Cypress", "chainId": 8217, "shortName": "Cypress", "chain": "KLAY", "network": "cipresso", "networkId": 8217, "nativeCurrency": {"name": "KLAY", "symbol": "KLAY", "decimals": 18}, "rpc": ["https://node-api.klaytnapi.com/v1/klaytn"], "faucets": [], "esploratori": [], "infoURL": "https://www.klaytn.com/" }, { "name": "KorthoTest", "chainId": 8285, "shortName": "Kortho", "chain": "Kortho", "test di rete", "networkId": 8285, "nativeCurrency": {"name": "Kortho Test", "symbol": "KTO", "decimals": 11}, "rpc": ["https://www.krotho-test.net"], "faucets": [], "esploratori": [], "infoURL": "https://www.kortho.io/" }, { "name": "GateChain Testnet", "chainId": 85, "shortName": "GTC-T", "chain": "gatechain", "network": "testnet", "networkId": 85, "nativeCurrency": {"name": "GateToken", "symbol": "GT", "decimals": 18}, "rpc": ["https://testnet.gatenode.cc"], "faucets": ["https://www.gatescan.org/testnet/faucet"], "explorers": [{"name": "GateScan", "url": "https://www.gatescan.org/testnet", "standard": "EIP3091"}], "infoURL": "https://www.gatechain.io" }, { "name": "GateChain Mainnet", "chainId": 86, "shortName": "GTC", "chain": "gatechain", "network": "mainnet", "networkId": 86, "nativeCurrency": {"name": "GateToken", "symbol": "GT", "decimals": 18}, "rpc": ["https://evm.gatenode.cc"], "faucets": ["https://www.gatescan.org/faucet"], "explorers": [{"name": "GateScan", "url": "https://www.gatescan.org", "standard": "EIP3091"}], "infoURL": "https://www.gatechain.io" }, { "name": "TomoChain", "chainId": 88, "shortName": "tomo", "chain": "TOMO", "network": "mainnet", "networkId": 88, "nativeCurrency": {"name": "TomoChain Ether", "symbol": "TOMO", "decimals": 18}, "rpc": ["https://rpc.tomochain.com"], "faucets": [], "esploratori": [], "infoURL": "https://tomocoin.io" }, { "name": "Wanchain", "chainId": 888, "shortName": "wan", "chain": "WAN", "network": "mainnet", "networkId": 888, "nativeCurrency": {"name": "Wancoin", "symbol": "WAN", "decimals": 18}, "rpc": ["https://gwan-ssl.wandevs.org:56891/"], "faucets": [], "esploratori": [], "infoURL": "https://www.wanscan.org" }, { "name": "bloxberg", "chainId": 8995, "shortName": "berg", "chain": "bloxberg", "network": "mainnet", "networkId": 8995, "nativeCurrency": {"name": "BERG", "symbol": "U + 25B3", "decimals": 18}, "rpc": ["https://core.bloxberg.org"], "faucets": ["https://faucet.bloxberg.org/"], "esploratori": [], "infoURL": "https://bloxberg.org" }, { "nome": "Ubiq Network Testnet", "chainId": 9, "shortName": "tubq", "chain": "UBQ", "network": "mainnet", "networkId": 2, "nativeCurrency": {"name": "Ubiq Testnet Ether", "symbol": "TUBQ", "decimals": 18}, "rpc": [], "faucets": [], "esploratori": [], "infoURL": "https://ethersocial.org" }, { "nome": "Binance Smart Chain Testnet", "chainId": 97, "shortName": "bnbt", "chain": "BSC", "network": "Chapel", "networkId": 97, "nativeCurrency": {"name": "Binance Chain Native Token", "symbol": "tBNB", "decimals": 18}, "rpc": ["https://data-seed-prebsc-1-s1.binance.org:8545","https://data-seed-prebsc-2-s1.binance.org:8545", " https://data-seed-prebsc-1-s2.binance.org:8545","https://data-seed-prebsc-2-s2.binance.org:8545","https://data- seed-prebsc-1-s3.binance.org:8545","https://data-seed-prebsc-2-s3.binance.org:8545 "], "faucets": ["https://testnet.binance.org/faucet-smart"], "explorers": [{"name": "bscscan-testnet", "url": "https://testnet.bscscan.com", "standard": "EIP3091"}], "infoURL": "https://testnet.binance.org/" }, { "name": "Nepal Blockchain Network", "chainId": 977, "shortName": "yeti", "chain": "YETI", "network": "mainnet", "networkId": 977, "nativeCurrency": {"name": "Nepal Blockchain Network Ether", "symbol": "YETI", "decimals": 18}, "rpc": ["https://api.nepalblockchain.dev", "https://api.nepalblockchain.network"], "faucets": ["https://faucet.nepalblockchain.network"], "esploratori": [], "infoURL": "https://nepalblockchain.network" }, { "name": "POA Network Core", "chainId": 99, "shortName": "skl", "chain": "POA", "network": "core", "networkId": 99, "nativeCurrency": {"name": "POA Network Core Ether", "symbol": "SKL", "decimals": 18}, "rpc": ["https://core.poanetwork.dev", "http://core.poanetwork.dev:8545", "https://core.poa.network", "ws: // core. poanetwork.dev:8546 "], "faucets": [], "esploratori": [], "infoURL": "https://poa.network" }, { "name": "Joys Digital TestNet", "chainId": 99415706, "shortName": "TOYS", "chain": "TOYS", "network": "testnet", "networkId": 99415706, "nativeCurrency": {"name": "TOYS", "symbol": "TOYS", "decimals": 18}, "rpc": ["https://toys.joys.cash/"], "faucets": ["https://faucet.joys.digital/"], "esploratori": [], "infoURL": "https://joys.digital" }, { "name": "Wanchain Testnet", "chainId": 999, "shortName": "twan", "chain": "WAN", "network": "testnet", "networkId": 999, "nativeCurrency": {"name": "Wancoin", "symbol": "WAN", "decimals": 18}, "rpc": ["https://gwan-ssl.wandevs.org:46891/"], "faucets": [], "esploratori": [], "infoURL": "https://testnet.wanscan.org" } ]

Apache-2.0

Updated 1 month ago

foundation-v2-bitcoin

blinkhash

❤️40

A scalable stratum pool for Bitcoin that interfaces with other modules in the Foundation project

GPL-3.0

JavaScript

Updated 4 months ago

foundationstratumv2

Pricecoin

zachchan105

❤️40

The earliest system of the Pricecoin releases. Pricecoin was originally written on the .8 codebase of Bitcoin. This gave us a foundational understanding on how the early releases of Bitcoin operated

MIT

C++

Updated 4 years ago

cryptocurrenciescryptocurrencylitecoin+3

tedcoin-immutable-voting-system

tedchain

❤️35

Tedchain is a immutable voting system project, with the goal of providing a long-term energy-efficient Proof of Stake based cryptocurrency. Built on the foundation of Bitcoin, innovations such as proof-of-stake help further advance the field of cryptocurrency.

C++

Updated 6 years ago

tedcoin-energy-efficient

tedchain

❤️35

Tedcoin is energy efficient project derived from Tedchain, with the goal of providing a long-term energy-efficient Proof of Stake crypto-currency. Built on the foundation of Bitcoin, innovations such as proof-of-stake help further advance the field of cryptocurrency.

C++

Updated 6 years ago

bitcoin-education-curriculum

BitcoinEdFoundation

❤️40

A free, open-source 6-module Bitcoin curriculum for students, educators, and independent learners. Built by The Bitcoin Education Foundation.

NOASSERTION

Updated 4 months ago

bitcoincurriculumeducation+4

Bitcoin-Price-Prediction-Using-Bayesian-Regression

gauravsummer

❤️35

The project is about predicting the price variations of bitcoin. These predictions could be used as the foundation of a bitcoin trading strategy.

Python

Updated 3 years ago

bitcoin-predictor

IVerse-VDV

🧡50

Open-source Bitcoin price predictor with deep learning methods. Foundation for ML enthusiasts to learn and contribute to crypto prediction algorithms. Smart Bitcoin price prediction with sleek interface - 7 day analysis, neural networks, and 70% accuracy. Your playground for crypto AI experimentation.

MIT

Jupyter Notebook

Updated 1 month ago

aiai-tradingbitcoin+10

Plasma-Project7

Alexpro780

❤️20

This repository contains the core structure of the Plasma Project, including documentation, source code, and licensing files. It serves as a foundation for developing and deploying an EVM-compatible blockchain platform secured by Bitcoin, designed for real-world asset tokenization and scalable smart contract execution.

Updated 4 months ago

causes.cash

baby636

❤️40

MIT

Updated 6 months ago

Bitcoin-Price-variation-prediction

Priyankha12

❤️35

In this project, I predicted the price variations of bitcoin, a virtual cryptographic currency. The predictions could be used as the foundation of a bitcoin trading strategy. To make the predictions I used the machine learning technique of Bayesian Regression for Latent Source Model, and implemented this technique in Python.

Jupyter Notebook

Updated 1 year ago

soulvan-coin-core

44547

❤️25

Soulvan Coin: A Scalable, Secure, and Decentralized Future for Digital Currency Soulvan Coin is a next-generation cryptocurrency built on the foundational principles of decentralization, peer-to-peer exchange, and open participation. Inspired by the Bitcoin protocol,

MIT

TypeScript

Updated 3 months ago

Chinese-currency

XYGDeveloper

❤️40

The China Dollar Digital Asset Exchange is a global professional digital asset trading platform, headquartered in Bangkok, Thailand. The exchange has obtained the national license of the Digital Money Exchange issued by the Thai government, and is one of the most authoritative, legal, efficient and transparent digital currency trading institutions in the industry. The team has many top security technicians and has built many cloud data centers by itself. It adopts the security technology of the same level as Nasdaq in the United States and the data tolerance scheme of separating main and standby data. It fully guarantees the security of assets. By using KUBERNETS scheduling technology, it realizes "second-speed transaction" and 2-minute quick cash withdrawal, supports tens of millions of people to operate online simultaneously, and brings users the ultimate experience. Relying on the advantages of its own enterprises and professionals, the China Dollar Digital Asset Exchange has always maintained its high-speed development, which has attracted the attention and trust of global investors. Its business scope has extended to a variety of fields, such as trading, media and scene technology. It also focuses on creating a "1+5" ecosystem, i.e. trading-centered, actively exploiting media, payment, community, intelligence, public welfare foundation research, etc. Five major sectors, to provide customers with more professional, safe, efficient and convenient quality services. The China Dollar Digital Asset Exchange is mainly aimed at global users. It provides many mainstream digital asset trading services, such as Bitcoin and ETF, and strives to build a secure, transparent, honest and efficient block chain digital asset trading platform.

MIT

Objective-C

Updated 2 years ago

Solareum-Blockchain-Platform-Poised-to-Change-Puerto-Rico-into-a-Solar-Powered-Country-

Solareum

❤️35

The Solareum project has taken it upon itself to transform Puerto Rico into a solar-powered island. The chairman of the Bitcoin Foundation, Mr. Brock Pierce was present at the recently held Restart week in Rincon. Addressing a crowd made up of crypto enthusiasts, investors and students, innovators and more, Mr. Pierce stated that his solar project for the Puerto Rico people is solely on a philanthropic basis. The entire crowd applauded his initiative and his love for the nation. The CMO of Solareum, Justin Lally said that: “Brock is the reason I am here, his passion for the island, people and what can be accomplished here, this trip will be a game changer in many ways. As a business partner and longtime friend of Mr. Pierce, intentions are beyond genuine, and we are set to make this a fully self-sustainable island.” With Pierce’s passion for Puerto Rico, Lally is convinced that the team could achieve great things in the island nation. “Actions speak louder than words, Solareum.club which offers solar panels all over the world, Solareum will have them installed and ready to give back power for free. Solareum is going to join the cryptocurrency community at the end of June and will be traded on various Exchanges. The token will be traded under the symbol SLRM,” Lally said, adding “Could you imagine if there was solar power prior to the hurricane, the island would bounce back in record time. So Solareum is going to join Mr. Pierce and other innovators that are looking to revamp the island, for the betterment of the people of the people and the island.” Everyone was quite impressed by Mr. Lally’s speech. He also reiterated that: “Solareum is the first of its kind. As you can see on the website Solareum.club, Mr. Pierce and I, only have the best intentions for this island, so over the course of the rest of the year, we will be donating solar panels to key areas, so no one goes without power for weeks on end as they previously have, ever again.” The Solareum project is focused on providing the world with clean, renewable energy products. It offers both P2P and B2B business models. Solareum is open to partnerships, and its blockchain system fosters trust and reliability. For more information visit https://www.solareum.club Whitepaper: https://docs.wixstatic.com Twitter : https://twitter.com/SOLAREUMclub LinkedIn: https://www.linkedin.com/company/solareum/ Instagram: https://www.instagram.com/solareumclub/ Email: [email protected]

Updated 2 years ago

0xBitcoinFoundation.org

BKW1882

❤️35

Foundation website

Updated 7 years ago