You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Forcerelay is now in active development stage and has a lot of things to do.
Currently we accomplished the creation of connection and channel layer between Axon and Ckb in CI, and so dose the creation of packet layer only in Ckb, so here is the further TODO checklist in both of relayer, contract, document and acceptance components:
add Axon and Ckb compatible secret keys management logic in forcerelay keys command
check Axon and Ckb's unimplemented methods in Endpoint trait, some of them might not to be completed because of the unnecessary telemetry query requirements @jjyr
write script to send message to business module contract (done forcerelay-ckb-sdk sudt-transfer example) @blckngm@ashuralyk
implement cell-existence proof check in Ckb light client once Ckb integrated live-cell mpt root in its header (work with Axon system contract)
replaced by Axon precomplied contracts: ckb_blake2b & verify_mmr_proof
(to be discussed) design and accomplish TypeId contract to use different type hash to mark a group of IBC cells (coming up with IBC Utility contract in the future, maybe)
add type id script into ckb contracts to generate a unique IBC-ID to eliminate fake cells attack(optional)
-> See also Forcerealy IBC state(SMT) rollup solution
Acceptance of Forcerelay/Axon
deploy solidity contracts and ckb contracts manually and start a standalone forcerelay server to test the message relay in the real world
(P-Medium) check the security of the design of Ckb contracts, which contains but not limited by the fake IBC cells and fake light client proofs, etc
(P-Low) concurrently create connection, channel and packet to test the stability of forcerelay
(P-Low) check the case of insufficient ckb of forcerelay
Construct a test scenario and try to spend all the CKB of the relayer
The text was updated successfully, but these errors were encountered:
ashuralyk
changed the title
**[TODO]** Upcoming todo list of unimplemented features and issues in Forcerelay/Axon
[TODO] Upcoming todo list of unimplemented features and issues in Forcerelay/Axon
Sep 7, 2023
ashuralyk
changed the title
[TODO] Upcoming todo list of unimplemented features and issues in Forcerelay/Axon
[TODO] unimplemented features and issues in Forcerelay/Axon
Sep 7, 2023
Forcerelay is now in active development stage and has a lot of things to do.
Currently we accomplished the creation of connection and channel layer between Axon and Ckb in CI, and so dose the creation of packet layer only in Ckb, so here is the further TODO checklist in both of relayer, contract, document and acceptance components:
In the relayer of Forcerelay/Axon
test: Add packet test for Axon #330
forcerelay keys
commandAxonTools::verify_mpt_proof
after Axon's bug fixed #264integrate cell-emitter runtime in Ckb monitor and relay Ckb headers and filtered cells to Axon system contractIn the Solidity contract of Forcerelay/Axon
replace truffle framework with hardhat@15168316096implement cell-existence proof check in Ckb light client once Ckb integrated live-cell mpt root in its header (work with Axon system contract)replaced by Axon precomplied contracts: ckb_blake2b & verify_mmr_proof
In the CKB contract of Forcerelay/Axon
ckb-ics
repoclient_id
andport_id
from h256 to arbitrary string, which increases the compatibility of Ckb with IBC protocol [refactor] add a new client cell and a new port cell to makeibc-ckb-contract
compatible with IBC protocol ckb-ics#7-> See also Forcerealy IBC state(SMT) rollup solution
Acceptance of Forcerelay/Axon
Done
In the document of Forcerelay/Axon
README.md
for forcerelay, which contains introduction, high level design, simplified deployment/config instructions and todo list #327README.md
for solidity contractREADME.md
for ckb contractREADME.md
for forcerelay-ckb-sdk @blckngmdocs: write a simple README for forcerelay-ckb-sdk forcerelay-ckb-sdk#6
The text was updated successfully, but these errors were encountered: