CA, TreasuryCap and ids

Contract: 0x80f9b6215ae18ed1a77f5d5153c4327fd48e17dbbcd12cde06b94dd2b95e3b18

MoomeBank: 0x19726370b573a350aa0fc7593da9ff49914e08270319dd4b10e708494e94e7e3

Coin: 0x80f9b6215ae18ed1a77f5d5153c4327fd48e17dbbcd12cde06b94dd2b95e3b18::moome::MOOME

Publish Package TX: Ad8wKQpSAxNWPEUxbBmWWbCbhwpzZ8QguQizaWSXhdr

Initial mint into buyback pool: JBryeQczbc6xXiWD7c5n2h2r7ARmnDTbWu3DPwMnYGjo

Buyback pool position burned: FTJuxdSWty9d5U8ADEuFUmpdbprWeeHb4Jjoo6ALFsnS

dApp: https://www.moome.pro/

Moome NFT type: 0x0c97111059ffdac078be82715fb6b6aaee472626b04a50c9002c84d66d5b2fe3::token::Moome

Swap: on turbos

Where is MOOME TreasuryCap?

The TreasuryCap of Moome is wrapped inside an IPXTreasuryStandard object, which is stored in MoomeBank in the LockedSupply object field.

This ensures that access to MintCap or BurnCap is strictly controlled and can only be obtained through Moome’s smart contract methods. These methods are available to execute from the dApp as 'stake' and 'unstake' actions, ensuring compliance with the IPX Coin Standard for secure and industry-best token functionality.