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
The most critical use for stucked txs occurs due to attacks and exploits. Like any malicious cw721 contract could resend on ACK response another transfer on both sides. This is one of other possibilities in forcing to congested channels.
Stuck txs - specifically means sending tons of IBC packets back and forth through a channel. This leads into tons of packets being queued for a channel. Relayers take these packets for a channel in FIFO style and relays them to the other chain back and forth.
So the best way is having packets being governed and controlled. Packets send to a channel is done by an IBC port: in this case it is the NFT module or ICS721 contract. Governance and controlling packets can be done on 2 occassion, both initially triggered by a send packet:
Collection (sender) passing NFT to ICS721 (nft module or wasm contract)
ICS721 sends packet to channel to IBC port on other chain
Governance in this case means whitelisting both cases:
only whitelisted senders (collections) are eligible to call ICS721
only whitelisted channels will be used for transfer
The most critical use for stucked txs occurs due to attacks and exploits. Like any malicious cw721 contract could resend on ACK response another transfer on both sides. This is one of other possibilities in forcing to congested channels.
Stuck txs - specifically means sending tons of IBC packets back and forth through a channel. This leads into tons of packets being queued for a channel. Relayers take these packets for a channel in FIFO style and relays them to the other chain back and forth.
So the best way is having packets being governed and controlled. Packets send to a channel is done by an IBC port: in this case it is the NFT module or ICS721 contract. Governance and controlling packets can be done on 2 occassion, both initially triggered by a send packet:
Governance in this case means whitelisting both cases:
Ark Protocol has contributed 4 contracts, acting as CW721 and ICS721 proxies: https://github.com/arkprotocol/cw721-proxy/tree/sender-whitelist
These contracts can be passed as proxies for ICS721 here:
All 4 contracts are using these WL packages:
https://github.com/arkprotocol/cw721-proxy/blob/sender-whitelist/packages/cw721-whitelist/src/lib.rs
https://github.com/arkprotocol/cw721-proxy/blob/sender-whitelist/packages/cw721-whitelist-map/src/lib.rs
These packages allows to be used in contracts for whitelisting and governance of ICS721.
PR for contributing back to @0xekez' implementation as public good ( #712 ) and open source it: 0xekez/cw721-proxy#1
Please also not @0xekez rate limiter proxy: https://github.com/0xekez/cw721-proxy/tree/main/contracts/cw721-rate-limited-proxy
The text was updated successfully, but these errors were encountered: