This is the testframework for Poly ecosystem which can send cross-chain transacions and check it status. Let's call this tool PIT for short.
There is two parts about PIT. First part including five functions is for create and setup cross-chain environment. Like creating accounts on chains and deploying contracts. Second part is for running testcases like sending cross-chain transactions.
PIT can help you build your cross-chain environment and providing examples about writing code to send cross-chain transacion.
The code is still under development.
| Part | Func | Desc |
|---|---|---|
| 1 | btc_prepare | Generate BTC multi-signature address and other information (you can also use existing multi-signature), deploy and bind BTCX contracts on each chain, and register BTCX contracts and transaction parameters with Poly. |
| 1 | eth_deployer | Two functions: deploy all the contracts on the Ethereum chain, from ECCM to each asset; to set up the binding of the contract, other chains need to complete the deployment first to ensure that the contract hash has been filled in the config file. |
| 1 | ont_deployer | Same as eth_deployer |
| 1 | cosmos_prepare | Initialize the chains based on COSMOS-SDK like Switcheo, create each asset and complete asset binding. |
| 1 | tools | Register the sidechain with Poly and sync the genesis block between chains. |
| 2 | cctest | Run testcases. |
Before you try the testcase or other functions, you need to finish the configuration file:
{
###
# This is BTC related settings
"BtcRestAddr": "http://ip:port", # BTC node
"BtcRestUser": "test",
"BtcRestPwd": "test",
"BtcFee": 1500,
"BtcRedeem": "552102dec9a415b6384ec0a9331d0cdf02020f0f1e5731c327b86e2b5a92455a289748210365b1066bcfa21987c3e207b92e309b95ca6bee5f1133cf04d6ed4ed265eafdbc21031104e387cd1a103c27fdc8a52d5c68dec25ddfb2f574fbdca405edfd8c5187de21031fdb4b44a9f20883aff505009ebc18702774c105cb04b1eecebcb294d404b1cb210387cda955196cc2b2fc0adbbbac1776f8de77b563c6d2a06a77d96457dc3d0d1f2102dd7767b6a7cc83693343ba721e0f5f4c7b4b8d85eeb7aec20d227625ec0f59d321034ad129efdab75061e8d4def08f5911495af2dae6d3e9a4b6e7aeb5186fa432fc57ae", # Multi-sign Redeem script(testnet)
"BtcNetType": "test", # Network Type
"BtcMultiSigNum": 7, # Multi-signature total
"BtcMultiSigRequire": 5, # Minimum number of multi-signatures
"BtcEncryptedPrivateKeyFile": "./btcprivk", # Multi-signature encrypted wallet storage path
"BtcEncryptedPrivateKeyPwd": "123",
"BtcVendorSigningToolConfFile": "./vendor_tool.json", # vendor configuration file
"BtcFeeRate": 10, # Multi-signature rate, when BTC returns to Bitcoin, unlock transaction rate
"BtcMinChange": 8000, # Multi-sign the minimum UTXO value allowed in the Poly chain contract
"BtcMinOutputValFromContract": 10000, # The minimum allowable withdrawal amount in the BTCX contract
"BtcSignerPrivateKey": "cRRMYvoHPN...MVwyqZVrAcX", # BTC simulates the private key for sending transactions
"BtcExistingVendorPrivks": "cREJsmv4W9Lr4Qh...wRoSnpxryGRL92N,cVJqF57c...PCwBDymEk,cTfnpP7C...pvWthPRoB3yGwR", # Existing multi-signature wallet private key
###
###
# eth
"EthURL": "http://ip:port", # Ethereum node
"ETHPrivateKey": "AEC101ECD...BE90B2A2608A9", # Etherem simulates the private key of the transaction
###
###
# Ontology
"OntJsonRpcAddress": "http://ip:port", # Ontology
"OntWallet": "./wallet.dat",
"OntWalletPassword": "pwd",
"GasPrice": 2500,
"GasLimit": 30000000,
"OntContractsAvmPath": "./avm", # Avm of all ontology contracts
###
###
# cosmos
"CMWalletPath": "./cosmos_key",#
"CMWalletPwd": "pwd",
"CMRpcUrl": "http://ip:port",
"CMChainId": "cosmos-gaia",
"CMGasPrice": "0.00001stake",
"CMGas": 200000,
"CMCrossChainId": 1000,
###
###
# Poly
"RCWallet": "./wallet.dat",
"RCWalletPwd": "pwd",
"RchainJsonRpcAddress": "http://ip:port",
###
###
# configuration for sending tx
"ReportInterval": 10,
"ReportDir": "./report", # Test case status report
"BatchTxNum": 100, # Batch send transaction: how many batches
"BatchInterval": 1, # Time interval for batch sending
"TxNumPerBatch": 100, # How many transactions per batch
###
###
# This part is the contract configuration for each chain.
# After deployment, it is automatically written.
# follows are contracts for testnet
"EthErc20": "0x33fb970bE14548309bbbdcbFe6327865C6d71b70",
"EthOep4": "0xde5dBad6ab0FD0EBDEBf6B6cf4eB93D51207dc8f",
"Eccd": "0xA38366d552672556CE82426Da5031E2Ae0598dcD",
"Eccm": "0xcF9b45217192F70c1df42Ba460Fd644FDB248eA5",
"Eccmp": "0xb600c8a2e8852832B75DB9Da1A3A1c173eAb28d8",
"EthLockProxy": "0xE44dDbAb7a9Aa11b9D0cA8b686F9E0299DB735d1",
"EthOngx": "0x0A03605ad4E8381855cF7b650f9482002267ad33",
"EthOntx": "0x8cE92808118Bc43c2B8635d3eb6b1b67cD2fB9a0",
"BtceContractAddress": "0x92705a16815A3d1AEC3cE9Cc273C5aa302961FcC",
"OntErc20": "e930755b130dccb25dc3cfee2b2e30d9370c1a75",
"OntOep4": "969850e009b5e2a061694f3479ec8e44bc68bcd3",
"OntLockProxy": "34a593c5ccfb8590e9a4bc7018529016aa4a55ad",
"OntEth": "ec2e25c4c12371ca37b129477a23a152e62ff103",
"BtcoContractAddress": "814d32455c21bfc25c33b75ccbfc34fe8e79bff1",
"CMLockProxy": "f71b55ef55cedc91fd007f7a9ba386ec978f3aa8",
###
###
# Test transaction limit. The cross-chain amount would not be over the limit.
"BtcValLimit": 100000,
"OntValLimit": 100,
"OngValLimit": 100000,
"EthValLimit": 10000000,
"Oep4ValLimit": 10000000,
"Erc20ValLimit": 10000000
###
}
Build the cctest like follow:
go build -o cctest cmd/cctest/main.go
You can run a testcase like:
./cctest -cfg=your_config_file -t case_name
Some cases:
| Case Name | Desc |
|---|---|
| SendOntToEthChain | Send ONT to ethereum. Contract EthOntx will receive your ONT. |
| SendOnteToOntChain | Send ONT back to ontology. It would transfer from EthOntx to Ontology. |
| SendEthToOntChain | Send ETH to ontology. Contract OntEth will receive your ETH. |
| SendEthoToEthChain | Send ETH back to ethereum. |
| SendBtcToOntChain | Send BTC to ontology. Contract BtcoContractAddress will mint a reflection coin BTCX for you. |
More case see here.
If you want more details about sending cross-chain transactions, you can read these documents
React
Typescript
Django
Laravel
Facebook
Microsoft
Google
Alibaba
D3
Tencent