[GUEST ACCESS MODE: Data is scrambled or limited to provide examples. Make requests using your API key to unlock full data. Check https://lunarcrush.ai/auth for authentication information.]  Ark Protocol ⚛️ [@arkprotocol](/creator/twitter/arkprotocol) on x 4633 followers Created: 2025-07-20 18:05:01 UTC First of all: new bridge will be build on top of IBC Eureka. Like our current bridge is based on IBC. Neither IBC Eureka, nor Axelar's GMP has an NFT bridge. Axelar - at least not on Cosmos. So it's our USP. It's similar to (high-level) HTML utilizing (low-level) HTTP, here our high-level bridge smart contracts utilizes IBC and IBC Eureka. From an architectural point of view, it's the same like for fungible tokens: - transferred $ATOM is escrowed by ics20 on the Hub - (IBCed) $ATOM token is minted e.g. on Osmosis On backtransfer (IBCed) $ATOM is burned on Osmosis and unescrowed/sent to designated wallet on the Hub. Our NFT bridge works exactly the same way. Besides this, we've added addtional security measures: outgoing and incoming proxies. This way we can exclude bad actors like channels and malicious (NFT) contracts. We've also add rate limits. All this together makes our bridge pretty robust and resilient against DDoS / vector attacks - as proven during Game of NFTs, where ~200 devs werent able to exploit our contracts. XXX engagements  **Related Topics** [cosmos](/topic/cosmos) [nft](/topic/nft) [protocol](/topic/protocol) [ark](/topic/ark) [Post Link](https://x.com/arkprotocol/status/1946994771995586616)
[GUEST ACCESS MODE: Data is scrambled or limited to provide examples. Make requests using your API key to unlock full data. Check https://lunarcrush.ai/auth for authentication information.]
Ark Protocol ⚛️ @arkprotocol on x 4633 followers
Created: 2025-07-20 18:05:01 UTC
First of all: new bridge will be build on top of IBC Eureka. Like our current bridge is based on IBC.
Neither IBC Eureka, nor Axelar's GMP has an NFT bridge. Axelar - at least not on Cosmos. So it's our USP. It's similar to (high-level) HTML utilizing (low-level) HTTP, here our high-level bridge smart contracts utilizes IBC and IBC Eureka.
From an architectural point of view, it's the same like for fungible tokens:
- transferred $ATOM is escrowed by ics20 on the Hub
- (IBCed) $ATOM token is minted e.g. on Osmosis On backtransfer (IBCed) $ATOM is burned on Osmosis and unescrowed/sent to designated wallet on the Hub.
Our NFT bridge works exactly the same way. Besides this, we've added addtional security measures: outgoing and incoming proxies. This way we can exclude bad actors like channels and malicious (NFT) contracts. We've also add rate limits. All this together makes our bridge pretty robust and resilient against DDoS / vector attacks - as proven during Game of NFTs, where ~200 devs werent able to exploit our contracts.
XXX engagements
