Polymarket is a prediction market
1. Built on CTF for conditional tokens (prediction shares)
2. Orderbook integrates with CTF for mint/redeem → deeper liquidity
3. Pricing via probabilities = intuitive UX
4. AA wallets improve onboarding
It separates the logic of OApp and the message bridge, enabling flexible OApp design. It also allows OApps to choose their own executor and DVN, offering great flexibility. The code is also beautifully written.
analyzed the implementation of LayerZero on SVM, it largely follows the design principles used on EVM, maintaining functional consistency.
https://t.co/iuYX5fLUpY
Even without asset delegation, in theory, it is still possible to build an NFT marketplace as sophisticated as OpenSea using Move, as well as implement lazy minting, allowing creators to mint NFTs with zero gas fees.
Additionally, Move’s lack of asset delegation significantly reduces flexibility. It remains uncertain whether this feature will be supported in the future.
The official implementation also highlights the power and flexibility of the Move language. However, there are some limitations, such as Sui not supporting operations like the approve function seen in ERC-20 tokens, which may limit certain scenarios.
The token standard is very flexible, allowing apps to define any rules for the assets they create. Additionally, conversion between tokens and coins is allowed (as long as the corresponding rules are met).
To approve the request, all the rules for the corresponding action must be approved. In order to approve these rules, the module that defines the rule must check and approve the action.
The overall process is as follows: The dApp contract implements the action logic and calls the sui::token module to create an action request. This request is a hot potato, meaning it must be processed by the corresponding function in the transaction or the transaction will fail.