Peera.

Explore

Connect with communities and discover new ideas.

Sui.X.Peera.

Earn Your Share of 1000 Sui

Gain Reputation Points & Get Rewards for Helping the Sui Community Grow.

Communities

Filter:All blockchains

Bounty

  • Xavier.eth.Peera.
    Xavier.eth303
    ForSuiJun 17, 2025
    +15

    How do ability constraints interact with dynamic fields in heterogeneous collections?

    I'm building a marketplace that needs to handle multiple asset types with different ability requirements, and I've hit some fundamental questions about Move's type system. I want to store different asset types in the same collection, but they have different abilities: Regular NFTs: key + store (transferable) Soulbound tokens: key only (non-transferable) Custom assets with transfer restrictions public struct Marketplace has key { id: UID, listings: Bag, // Want to store different asset types here } // This works for transferable assets public fun list_transferable( marketplace: &mut Marketplace, asset: T, price: u64 ) { /* ... */ } // But how to handle soulbound assets? public fun list_soulbound( // No store ability marketplace: &mut Marketplace, asset_ref: &T, // Can only take reference price: u64 ) { /* How do I store metadata about this? */ } Key Questions: Ability Requirements: When using dynamic_field::add(), does V always need store at compile time? Can wrapper types work around this? Heterogeneous Storage: Can a single Bag store objects with different ability sets (key + store + copy vs key + store), and handle them differently at runtime? Type Safety: Since dynamic fields perform type erasure, how do I maintain type safety when retrieving values? What's the pattern for storing type metadata? Witness Pattern: How do ability constraints work with phantom types? Can I store Asset and Asset in the same collection and extract type info later? Building a system where NFTs, soulbound tokens, and restricted assets all need marketplace functionality but with different transfer semantics. I’ve tried wrapper types, multiple collections per ability set, separate type metadata storage. Each has tradeoffs between type safety, gas costs, and complexity.

    0
    4
  • Peera Admin.Peera.
    Peera Admin37
    ForSuiMay 29, 2025
    +10

    Why does BCS require exact field order for deserialization when Move structs have named fields?

    Why does BCS require exact field order for deserialization when Move structs have named fields? I've been diving deep into BCS encoding/decoding in Move, particularly for cross-chain communication and off-chain data processing. While working through the examples in the Sui Move documentation, I encountered some behavior that seems counterintuitive and I'm trying to understand the underlying design decisions. According to the BCS specification, "there are no structs in BCS (since there are no types); the struct simply defines the order in which fields are serialized." This means when deserializing, we must use peel_* functions in the exact same order as the struct field definition. My Specific Questions: Design Rationale: Why does BCS require exact field order matching when Move structs have named fields? Wouldn't it be more robust to serialize field names alongside values, similar to JSON or other self-describing formats? Generic Type Interaction: The docs mention that "types containing generic type fields can be parsed up to the first generic type field." Consider this structure: struct ComplexObject has drop, copy { id: ID, owner: address, metadata: Metadata, generic_data: T, more_metadata: String, another_generic: U } How exactly does partial deserialization work here? Can I deserialize up to more_metadata and ignore both generic fields, or does the first generic field (generic_data) completely block further deserialization? Cross-Language Consistency: When using the @mysten/bcs JavaScript library to serialize data that will be consumed by Move contracts, what happens if: I accidentally reorder fields in the JavaScript object? The Move struct definition changes field order in a contract upgrade? I have nested structs with their own generic parameters? Practical Implications: In production systems, how do teams handle BCS schema evolution? Do you version your BCS schemas, or is the expectation that struct field order is immutable once deployed?

    5
    3
  • Peera Admin.Peera.
    Peera Admin31
    ForMoveMar 11, 2025
    +10

    Sui Move vs Aptos Move - What is the difference?

    Sui Move and Aptos Move - two prominent implementations of the Move programming language. While both are rooted in the same foundational principles, they have diverged significantly in design, execution, and ecosystem development. To better understand their differences, we need to uncover some of their key aspects: How do their runtimes differ? Both Sui and Aptos implement their own custom Move virtual machines (VMs). How does this impact performance, scalability, and developer experience? For instance: Does Sui's runtime optimize for parallel execution differently than Aptos'? Are there notable differences in transaction lifecycle management or gas models? What are the differences between their standard libraries? The Move standard library is a critical component for building smart contracts. However, Sui and Aptos have forked their implementations, leading to divergence: Are there modules or functions unique to one implementation but absent in the other? How do these differences affect common use cases like token creation, NFTs, or decentralized finance (DeFi)? How does data storage differ between them? One of the most significant distinctions lies in how Sui and Aptos handle data storage: Sui uses an object-centric model, where each object has its own ownership and permissions. Aptos, on the other hand, retains a more traditional account-based model similar to Ethereum. How does this impact state management, composability, and gas efficiency? Is it fair to say that Aptos is closer to EVM while Sui is closer to SVM? Some developers argue that Aptos' account-based architecture resembles Ethereum's EVM, while Sui's object-centric approach aligns more closely with Solana's SVM. Do you agree with this analogy? Why or why not? How does this architectural choice influence developer ergonomics and application design? Are there universal packages working for both Sui Move and Aptos Move? Given their shared origins, it would be ideal if some libraries or tools were interoperable across both ecosystems. Are there any existing universal packages or frameworks that work seamlessly on both platforms? If not, what are the main barriers to achieving compatibility? Can one of them be transpiled into another? If a project is built on Sui Move, could it theoretically be transpiled to run on Aptos Move, or vice versa? What are the technical challenges involved in such a process? Are there tools or compilers currently available to facilitate this kind of migration?

    2
    1

Newest

  • Evgeniy CRYPTOCOIN.Peera.
    Evgeniy CRYPTOCOIN10
    ForSuiJun 26, 2025

    Q: How to Properly Use the Sui SDK for Frontend Integration?

    I'm building a frontend (React/Next.js) for a Sui dApp and need to interact with the blockchain—fetching objects, sending transactions, and listening to events. I’ve tried using the @mysten/sui.js SDK, but I’m running into issues: Wallet Connection: Sometimes, the wallet doesn’t return the user’s address after connecting. Transaction Handling: Transactions fail silently or return vague errors. RPC Limits: I get rate-limited or timeouts when fetching large datasets. Real-Time Updates: How can I listen for on-chain events (e.g., NFT mints, balance changes)? What I’ve tried: ✔ Basic SuiClient setup with mainnet and testnet RPCs. ✔ Using useWallet() from @mysten/dapp-kit for wallet integration. ✔ Manual transaction signing with signAndExecuteTransactionBlock. Questions: What’s the recommended way to initialize the Sui SDK in a frontend app? How do I handle errors gracefully (e.g., RPC failures, wallet rejections)? Are there best practices for optimizing queries (batching, caching, etc.)? How can I subscribe to real-time updates (e.g., new transactions, object changes)? Expert Answer: Initializing the Sui SDK The @mysten/sui.js SDK should be configured with a reliable RPC endpoint. For production apps, consider: Default RPCs: ts import { SuiClient, getFullnodeUrl } from '@mysten/sui.js/client'; const client = new SuiClient({ url: getFullnodeUrl('mainnet') }); Fallback RPCs: Use services like Sui RPC Providers to avoid rate limits. For wallet integration, use @mysten/dapp-kit: tsx import { createNetworkConfig, SuiClientProvider, WalletProvider } from '@mysten/dapp-kit'; import { getFullnodeUrl } from '@mysten/sui.js/client'; const { networkConfig } = createNetworkConfig({ mainnet: { url: getFullnodeUrl('mainnet') }, testnet: { url: getFullnodeUrl('testnet') }, }); function App() { return ( ); } Handling Transactions & Errors Always wrap transactions in error handling: ts try { const tx = await signAndExecuteTransactionBlock({ transactionBlock: txBlock, options: { showEffects: true }, }); console.log("Tx Digest:", tx.digest); } catch (err) { console.error("Tx Failed:", err.message); // Handle specific errors (e.g., user rejection, insufficient gas) } Common errors: "User rejected the request" → Wallet popup was closed. "Gas budget exceeded" → Increase gas budget with txBlock.setGasBudget(). "Object not found" → Check if the object ID is correct and still exists. Optimizing RPC Calls Batching Requests: Use multiGetObjects for fetching multiple objects in one call. Caching: Use React Query or SWR to cache RPC responses: ts import { useSuiClientQuery } from '@mysten/dapp-kit'; const { data } = useSuiClientQuery('getObject', { id: objectId, options: { showContent: true }, }); Pagination: For large datasets, use suix_getDynamicFields with cursors. Real-Time Updates Use WebSockets or polling: WebSocket Subscriptions (advanced): ts const unsubscribe = client.subscribeEvent({ filter: { sender: '0x123...' }, onMessage(event) { console.log("New event:", event); }, }); // Cleanup on unmount return () => unsubscribe(); Polling with Hooks: ts useSuiClientSubscription('subscribeEvent', { filter: { eventType: 'ExampleEvent' }, onData(event) { console.log("Event:", event); }, }); Pro Tips Use @mysten/dapp-kit for pre-built wallet hooks. Set a custom gas budget for complex transactions. Monitor RPC health – switch endpoints if responses are slow. Test on Testnet before mainnet deployment.

    0
    0
  • Ramirez.Peera.
    Ramirez125
    ForSuiJun 26, 2025

    Why can't I find the SUI wallet on devices or website?

    I tried to locate my SUI wallet but I can't find it on any of my devices nor on the SUI main webpage. Has something changed about the wallet that I'm not aware of? Are there any recent updates or rebranding I should know about?

    0
    0
  • HaGiang.Peera.
    HaGiang180
    ForSuiJun 25, 2025

    How to integrate the Vue front-end framework into the sui ecosystem

    I'm currently working on a transformation of an old front-end project. The old project uses Vue as the front-end framework. How to connect to the wallet of the Sui ecosystem has always been a headache for me. In previous development, if I used the react framework, I could easily use the official one @mysten/dapp-kitto build a complete set of wallet connections, initiate transactions, and sign methods. Among the methods provided by mysten labs, there is @mysten/wallet-standard this library, which @mysten/suican be used to build the corresponding methods for wallet connection and signature transactions. The process of connecting to the wallet is as follows: Determine whether the user has connected to the wallet: initWallet() { const connectedWallet = window.localStorage.getItem("connectedWallet") const connectedAddress = window.localStorage.getItem("connectedAddress") if (connectedWallet && this.supportWallets.includes(connectedWallet) && connectedAddress) { this.connectWallet(connectedWallet) } } Connect your wallet // Connect Wallet (e.g., Slush) async connectWallet(walletName) { try { const availableWallets = getWallets().get(); let wallet = availableWallets.find(e => e.name === walletName); await wallet.features['standard:connect'].connect(); if (wallet.accounts.length > 0) { // Usually the first account is the currently active address const address = wallet.accounts[0].address; this.connectedWallet = wallet.name; this.address = address; window.localStorage.setItem("connectedAddress", address); window.localStorage.setItem("connectedWallet", wallet.name); } // Listen for wallet address changes or disconnection wallet.features['standard:events'].on('change', (event) => { // Logic for when the current wallet address doesn't match the stored address or when disconnected if (event.accounts.length === 0 || event.accounts[0].address !== this.address) { console.log('User changed accounts or disconnected...'); setTimeout(() => { window.localStorage.removeItem("connectedAddress"); window.localStorage.removeItem("connectedWallet"); window.location.reload(); }, 1000); } }); } catch (error) { console.log(error); } } The following is the transfer operation. All transactions can be wallet.features['sui:signTransaction'].signTransactionsigned: async transferSui() { try { const wallet = getWallets().get().find(e => e.name === this.connectedWallet) const amount = this.amount const toAddress = this.toAddress const tx = new Transaction() const [coin] = tx.splitCoins(tx.gas, [amount * 1e9]) tx.transferObjects([coin], toAddress) const { bytes, signature } = await wallet.features['sui:signTransaction'].signTransaction({ transaction: tx, account: wallet.accounts[0], chain: sui:${import.meta.env.VITE_SUPPORT_NETWORK} }); const executeRes = await suiClient.executeTransactionBlock({ transactionBlock: bytes, signature: signature, options: { showEffects: true, showObjectChanges: true, showBalanceChanges: true, showEvents: true, showInput: true } }); this.hash = executeRes.digest } catch (error) { console.log(error); } } Finally, you can create a function to disconnect the wallet on the web: async disconnectWallet() { try { const availableWallets = getWallets().get(); const walletName = window.localStorage.getItem("connectedWallet") let wallet = availableWallets.find(e => e.name === walletName) await wallet.features['standard:disconnect'].disconnect(); window.localStorage.removeItem("connectedAddress") window.localStorage.removeItem("connectedWallet") window.location.reload() } catch (error) { console.log('meet some errors '); } }, `

    2

Unanswered

  • Evgeniy CRYPTOCOIN.Peera.
    Evgeniy CRYPTOCOIN10
    ForSuiJun 26, 2025

    Q: How to Properly Use the Sui SDK for Frontend Integration?

    I'm building a frontend (React/Next.js) for a Sui dApp and need to interact with the blockchain—fetching objects, sending transactions, and listening to events. I’ve tried using the @mysten/sui.js SDK, but I’m running into issues: Wallet Connection: Sometimes, the wallet doesn’t return the user’s address after connecting. Transaction Handling: Transactions fail silently or return vague errors. RPC Limits: I get rate-limited or timeouts when fetching large datasets. Real-Time Updates: How can I listen for on-chain events (e.g., NFT mints, balance changes)? What I’ve tried: ✔ Basic SuiClient setup with mainnet and testnet RPCs. ✔ Using useWallet() from @mysten/dapp-kit for wallet integration. ✔ Manual transaction signing with signAndExecuteTransactionBlock. Questions: What’s the recommended way to initialize the Sui SDK in a frontend app? How do I handle errors gracefully (e.g., RPC failures, wallet rejections)? Are there best practices for optimizing queries (batching, caching, etc.)? How can I subscribe to real-time updates (e.g., new transactions, object changes)? Expert Answer: Initializing the Sui SDK The @mysten/sui.js SDK should be configured with a reliable RPC endpoint. For production apps, consider: Default RPCs: ts import { SuiClient, getFullnodeUrl } from '@mysten/sui.js/client'; const client = new SuiClient({ url: getFullnodeUrl('mainnet') }); Fallback RPCs: Use services like Sui RPC Providers to avoid rate limits. For wallet integration, use @mysten/dapp-kit: tsx import { createNetworkConfig, SuiClientProvider, WalletProvider } from '@mysten/dapp-kit'; import { getFullnodeUrl } from '@mysten/sui.js/client'; const { networkConfig } = createNetworkConfig({ mainnet: { url: getFullnodeUrl('mainnet') }, testnet: { url: getFullnodeUrl('testnet') }, }); function App() { return ( ); } Handling Transactions & Errors Always wrap transactions in error handling: ts try { const tx = await signAndExecuteTransactionBlock({ transactionBlock: txBlock, options: { showEffects: true }, }); console.log("Tx Digest:", tx.digest); } catch (err) { console.error("Tx Failed:", err.message); // Handle specific errors (e.g., user rejection, insufficient gas) } Common errors: "User rejected the request" → Wallet popup was closed. "Gas budget exceeded" → Increase gas budget with txBlock.setGasBudget(). "Object not found" → Check if the object ID is correct and still exists. Optimizing RPC Calls Batching Requests: Use multiGetObjects for fetching multiple objects in one call. Caching: Use React Query or SWR to cache RPC responses: ts import { useSuiClientQuery } from '@mysten/dapp-kit'; const { data } = useSuiClientQuery('getObject', { id: objectId, options: { showContent: true }, }); Pagination: For large datasets, use suix_getDynamicFields with cursors. Real-Time Updates Use WebSockets or polling: WebSocket Subscriptions (advanced): ts const unsubscribe = client.subscribeEvent({ filter: { sender: '0x123...' }, onMessage(event) { console.log("New event:", event); }, }); // Cleanup on unmount return () => unsubscribe(); Polling with Hooks: ts useSuiClientSubscription('subscribeEvent', { filter: { eventType: 'ExampleEvent' }, onData(event) { console.log("Event:", event); }, }); Pro Tips Use @mysten/dapp-kit for pre-built wallet hooks. Set a custom gas budget for complex transactions. Monitor RPC health – switch endpoints if responses are slow. Test on Testnet before mainnet deployment.

    0
    0
  • Ramirez.Peera.
    Ramirez125
    ForSuiJun 26, 2025

    Why can't I find the SUI wallet on devices or website?

    I tried to locate my SUI wallet but I can't find it on any of my devices nor on the SUI main webpage. Has something changed about the wallet that I'm not aware of? Are there any recent updates or rebranding I should know about?

    0
    0
  • MoonBags.Peera.
    MoonBags95
    ForSuiJun 24, 2025

    Let's build the ultimate list of Sui dev extensions! Share your must-haves. 🔥

    Just figrue out the link share from Suinami VS Code extension for Sui Move to Build, test, publish, call functions from a slider, rather than always using CLI Check it out: https://marketplace.visualstudio.com/items?itemName=blockchainBard.suimoverunner

    0
    0

Trending

  • 0xduckmove.Peera.
    0xduckmove413
    ForSuiApr 08, 2025

    👀 SEAL- I Think Web3 Data Privacy Is About to Change

    👀SEAL is Live on Sui Testnet – I Think Web3 Data Privacy Is About to Change In the Web3, it’s common to hear phrases like “users own their data” or “decentralized by design”. But when you look closely, many applications still rely on centralized infrastructures to handle sensitive data — using services like AWS or Google Cloud for key management. This introduces a contradiction: decentralization on the surface, centralization underneath. But what if there was a way to manage secrets securely, without giving up decentralization?Introducing SEAL – Decentralized Secrets Management (DSM), now live on the Sui Testnet. SEAL aims to fix one of Web3’s biggest hypocrisies: shouting decentralization while secretly using AWS You maybe ask me: What is SEAL? SEAL is a protocol that lets you manage sensitive data securely and decentrally – built specifically for the Web3 world. Think of it as a privacy-first access control layer that plugs into your dApp. You can think of SEAL as a kind of programmable lock for your data. You don’t just lock and unlock things manually — you write policies directly into your smart contracts, using Move on Sui. Let’s say you’re building a dApp where: Only NFT holders can unlock a premium tutorial Or maybe a DAO has to vote before sensitive files are revealed Or you want metadata to be time-locked and only accessible after a specific date SEAL makes all of that possible. The access control lives onchain, fully automated, no need for an admin to manage it. Just logic, baked right into the blockchain. SEAL makes all of that possible. The access control lives onchain, fully automated, no need for an admin to manage it. Just logic, baked right into the blockchain. Another interesting piece is how SEAL handles encryption. It uses something called threshold encryption, which means: no single node can decrypt the data. It takes a group of servers to work together — kinda like multi-sig, but for unlocking secrets. This distributes trust and avoids the usual single-point-of-failure problem. And to keep things truly private, SEAL encrypts and decrypts everything on the client side. Your data is never visible to any backend. It stays in your hands — literally — on your device. and SEAL doesn’t care where you store your data. Whether it’s IPFS, Arweave, Walrus, or some other platform, SEAL doesn’t try to control that part. It just focuses on who’s allowed to see what, not where things are stored. So yeah, it’s not just a library or API — it’s an onchain-first, access-controlled, privacy-by-default layer for your dApp. SEAL fills a pretty critical gap. Let’s break that down a bit more. If you’re building a dApp that deals with any form of sensitive data — gated content, user documents, encrypted messages, even time-locked NFT metadata — you’ll run into the same problem: ➡️ How do you manage access securely, without relying on a centralized service? Without something like SEAL, most teams either: Use centralized tools like AWS KMS or Firebase, which clearly goes against decentralization Or try to patch together half-baked encryption logic themselves, which usually ends up brittle and hard to audit https://x.com/EmanAbio/status/1908240279720841425?ref_src=twsrc%5Etfw%7Ctwcamp%5Etweetembed%7Ctwterm%5E1908240279720841425%7Ctwgr%5E697f93dc65359d0c8c7d64ddede66c0c4adeadf1%7Ctwcon%5Es1_&ref_url=https%3A%2F%2Fwww.notion.so%2Fharryph%2FSEAL-Launches-on-Sui-Testnet-1cc4f8e09bb380969c0dcc627b96cc22 Neither of those scales well. Especially not when you’re trying to build trustless apps across multiple chains or communities. SEAL makes that entire process modular and programmable. You define your access rules in Move smart contracts, and SEAL handles the rest — key generation, decryption approvals, and access enforcement — all without anyone manually issuing keys or running backend checks. Even better, those rules are auditable and immutable — once they’re onchain, they follow the contract, not a human admin. So instead of asking “who should manage access to this data?” you just ask: “What logic should define access?” …and let the chain handle it. Clean and scalable. That’s what makes SEAL relevant for more than just “security tools” — it’s a base layer for any dApp that cares about privacy, compliance, or dynamic access logic. It’s a small shift — but it changes a lot about how we think of data in Web3. Instead of encrypting after deployment, or relying on external services, you start with privacy built-in — and access handled entirely by smart contract logic. And that’s exactly what Web3 needs right now. How Does SEAL Actually Work? We’ve covered what SEAL is and why Web3 needs it, let’s take a look at how it’s actually built under the hood. This part is where things get more technical — but in a good way. The architecture is elegant once you see how all the pieces fit together. At a high level, SEAL works by combining onchain access logic with offchain key management, using a technique called Identity-Based Encryption (IBE). This allows devs to encrypt data to an identity, and then rely on smart contracts to define who is allowed to decrypt it. Step 1: Access Rules in Smart Contracts (on Sui) Everything starts with the smart contract. When you’re using SEAL, you define a function called seal_approve in your Move contract — this is where you write your conditions for decryption. For example, here’s a simple time-lock rule written in Move: entry fun seal_approve(id: vector, c: &clock::Clock) { let mut prepared: BCS = bcs::new(id); let t = prepared.peel_u64(); let leftovers = prepared.into_remainder_bytes(); assert!((leftovers.length() == 0) && (c.timestamp_ms() >= t), ENoAccess); } Once deployed, this contract acts as the gatekeeper. Whenever someone wants to decrypt data, their request will get checked against this logic. If it passes, the key gets released. If not, they’re blocked. No one has to intervene. Step 2: Identity-Based Encryption (IBE) Here’s where the magic happens. Instead of encrypting data for a specific wallet address (like with PGP or RSA), SEAL uses identity strings — meaning you encrypt to something like: 0xwalletaddress dao_voted:proposal_xyz PkgId_2025_05_01 (a timestamp-based rule) or even game_user_nft_holder When the data is encrypted, it looks like this: Encrypt(mpk, identity, message) mpk = master public key (known to everyone) identity = the logic-defined recipient message = the actual data Later, if someone wants to decrypt, the key server checks if they match the policy (via the seal_approve call onchain). If it’s approved, it returns a derived private key for that identity. Derive(msk, identity) → sk Decrypt(sk, encrypted_data) The user can then decrypt the content locally. So encryption is done without needing to know who will decrypt ahead of time. You just define the conditions, and SEAL figures out the rest later. It’s dynamic. Step 3: The Key Server – Offchain, But Not Centralized You might wonder: who’s holding these master keys? This is where SEAL’s Key Server comes in. Think of it as a backend that: Holds the master secret key (msk) Watches onchain contracts (like your seal_approve logic) Only issues derived keys if the conditions are satisfied But — and this is key — SEAL doesn’t rely on just one key server. You can run it in threshold mode, where multiple independent servers need to agree before a decryption key is issued. For example: 3-of-5 key servers must approve the request. This avoids central points of failure and allows decentralization at the key management layer too. Even better, in the future SEAL will support MPC (multi-party computation) and enclave-based setups (like TEE) — so you can get even stronger guarantees without compromising usability. Step 4: Client-Side Decryption Once the key is returned to the user, the actual decryption happens on their device. This means: The server never sees your data The backend never stores decrypted content Only the user can access the final message It’s a solid privacy model. Even if someone compromises the storage layer (IPFS, Arweave, etc.), they still can’t read the data without passing the access logic. Here’s the quick mental model: This structure makes it easy to build dApps where access rules aren’t hardcoded — they’re dynamic, auditable, and fully integrated into your chain logic. The Team Behind SEAL SEAL is led by Samczsun, a well-known figure in the blockchain security community. Formerly a Research Partner at Paradigm, he has audited and saved multiple ecosystems from major exploits. Now, he’s focused full-time on building SEAL into a core piece of Web3’s privacy infrastructure. With his background and credibility, SEAL is not just another experimental tool — it’s a serious attempt at making decentralized data privacy both practical and scalable. As SEAL goes live on the Sui Testnet, it brings a new standard for how Web3 applications can manage secrets. By combining onchain access control, threshold encryption, and client-side privacy, SEAL offers a more trustworthy foundation for decentralized data handling. Whether you’re building dApps, DAOs, or decentralized games — SEAL provides a powerful toolkit to enforce access control and protect user data without compromising on decentralization. If Web3 is going to move forward, secure infrastructure like SEAL is not optional — it’s essential

    8
  • Vens.sui.Peera.
    Vens.sui196
    ForSuiApr 29, 2025

    AMM Bot in Sui Ecosystem

    What are the key features and functionalities of AMM bots within the Sui ecosystem? How do they improve upon traditional trading mechanisms, and what advantages do they offer to users engaging with DeFi protocols on the Sui network? Do I need to build one or I can use Turbos Finance for example

    7
    2
  • MarlKey.Peera.
    MarlKey56
    ForSuiApr 30, 2025

    Is the only way to publish Move packages through an EOA?

    I assume there is no way on Sui chain as there is no module on chain which publishes packages.

    6
    3