This is all theory as it's not running yet, but unless they choose to obfuscate somehow, the movement along a DomainID is visible. How granular will have more to do with Bitso's orchestration than the ledger functions.

とても良い視点ですね💡今のところ話は出ていないように思います。（要調査） 技術的にDomainIDごとのAMMが必要になり、資格情報のガード処理など含めて、複雑化してしまうので、プロトコルアップデートの優先順位としては低いと判断されているのかなという所感です。 ※AMM v2の提案仕様である、トークンペア * カーブタイプ、さらにdomainIDの組み合わせ（キーレット）が作れるように追加が必要。

They are adding additional contextual information to the UserId, including DomainType (e.g. EXPERIENCE/OAUTH) and DomainId. I'm not sure what it means yet.

Any offer that has access to liquidity in a given Permissioned DEX will include a "DomainID" field indicating what domain it is in. xrpl.org/docs/concepts/token…

DomainID is included in the Single Asset Vault spec for permissioned lending. I have a number of other assorted ideas for the future as well: - XLS-87 is one example: github.com/XRPLF/XRPL-Standa… - Could expand Deposit Auth to support domains - Could use domains in Smart Escrow/Smart MPT flows (or other future programmability flows)

Ripple Payments hitting the XRPL DEX is a nothing short of revolutionary. You don't have to ask twice, so here are mine: 🔹Can story tell how end to end Ripple Payments would utilize the XRPL from Credentials to Permissioned DEX for their institutional clients? 🔹ZKP is a big focus, how do you envision privacy to work with Ripple Payments and the Permissioned DEX/Domain? 🔹Can you explain the different Permissioned DEX modes: - Open Offers - Hybrid Offers - Permissioned Offers 🔹We see a lot use of the DomainID by Permissioned Domain, e.g the DEX or for Token Authorization. What other features would get the functionality of specifying a DomainID for compliant lvl use? 🔹What type Credentials are most useful for institutional usage of Permissioned Domain e.g KYC? 🔹What are the advantages for traditional finance and markets to come on chain using compliance stack of the XRPL (e.g via Ripple Payments) vs just staying in traditional finance? 🔹Permissioned DEX is only for the Orderbook (CLOB) not for the AMM. Is this a barrier for institutional usage or is the Orderbook enough?

NEAR GITHUB UPDATES [07.10.2025] 📟 What shipped on the @nearprotocol GitHub today? Here’s the latest from the NEAR devs! 1/ BULK MEMORY FEES - nearcore What changed: • Introduced dedicated parameters for bulk memory/table operations fees: `linear_op_base_cost` and `linear_op_unit_cost`. • Updated gas costs for bulk memory/table operations to match the latest `wasm_regular_op_cost` values (3_856_371 per unit and 123_403_872 base cost). Why it matters: This pull request (github.com/near/nearcore/pul…) refines gas fee calculations for bulk memory/table operations, replacing the previous generic `regular_op_cost` with specific parameters, ensuring more accurate gas accounting. Check out the full repo: github.com/near/nearcore 2/ FEATURE DEPRECATION - nearcore What changed: • Deprecated GlobalContracts feature • Deprecated BlockHeightForReceiptId feature • Deprecated ProduceOptimisticBlock feature Why it matters: This pull request (github.com/near/nearcore/pul…) removes outdated features as mainnet has reached protocol version 80, simplifying the codebase and reducing maintenance overhead. Check out the full repo: github.com/near/nearcore 3/ DEPRECATE FEATURE - nearcore: VersionedStateWitness What changed: • Deprecated the VersionedStateWitness protocol feature. • Removed ChunkStateWitnessV1 from the codebase. Why it matters: This pull request (github.com/near/nearcore/pul…) simplifies the state witness handling by removing outdated features, reducing complexity in the validation process. Check out the full repo: github.com/near/nearcore 4/ PERFORMANCE OPTIMIZATION - nearcore: Switch to hashmap for trie changes tracker What changed: • Replaced ordered maps with hashed maps in `apply_chunk` components. • Modified `core/store/src/trie/mod.rs` and `core/store/src/trie/mem/memtrie_update.rs` for improved efficiency. Why it matters: This pull request (github.com/near/nearcore/pul…) results in a 2% higher stable TPS, optimizing the performance of trie changes tracking. Check out the full repo: github.com/near/nearcore 5/ TOKEN-ID REFACTOR - intents What changed: • Introduced a separate `token-id` crate for TokenId utilities. • Re-exported TokenId for NEP-171 and NEP-245, simplifying imports. • Unified TokenId types across APIs for consistency. • Updated legacy tests to align with new import paths. Why it matters: This pull request (github.com/near/intents/pull…) improves code organization and simplifies TokenId usage across the project, particularly for NEP-171 and NEP-245 standards. Check out the full repo: github.com/near/intents 6/ PUBLICKEY TYPE - mpc: Introduced dtos_contract::PublicKey What changed: • Introduced a new `dtos_contract::PublicKey` type to replace `near_sdk::PublicKey` where possible. • Added temporary conversion functions for compatibility. • Updated several modules to handle the new type. Why it matters: This pull request (github.com/near/mpc/pull/122…) standardizes key handling across the codebase, reducing dependency on `near_sdk::PublicKey` and improving code maintainability. Check out the full repo: github.com/near/mpc 7/ PUBLIC KEY SERIALIZATION - mpc: Base58 encoding for node HTTP server. What changed: • Added base58 encoding for public key serialization in the node HTTP server. • Introduced new `node-types` module for handling node-specific types. • Refactored HTTP server tests using Given/When/Then sections. • Added snapshot tests for serialization. • Moved serialization logic to a separate file. Why it matters: This pull request (github.com/near/mpc/pull/123…) standardizes public key serialization using base58, improving consistency and compatibility with NEAR ecosystem tools. Check out the full repo: github.com/near/mpc 8/ FIX TOKIO RUNTIME - mpc What changed: • Ensures attestation requests run within a tokio runtime context by modifying `StartCmd::run`. • Prevents node startup panic caused by missing runtime context. Why it matters: This pull request (github.com/near/mpc/pull/122…) resolves a critical issue that previously caused the MPC node to panic during startup, ensuring stable operation for attestation requests. Check out the full repo: github.com/near/mpc 9/ METRICS ADDED - mpc: Track participant IDs in failed signatures What changed: • Added metrics to track participant IDs in failed ECDSA signature computations. • Added metrics to track participant IDs in failed EdDSA signature computations. Why it matters: This pull request (github.com/near/mpc/pull/123…) improves debugging capabilities by identifying participants involved in failed signature computations, enhancing the reliability of MPC operations. Check out the full repo: github.com/near/mpc 10/ KEYSHARE IMPROVEMENTS - mpc What changed: • Added consistency checks in `PermanentKeyStorage` to prevent inconsistent keyshares across epochs. • Introduced a constructor for `PermanentKeyshareData` to enforce ordering by `DomainId`. Why it matters: This pull request (github.com/near/mpc/pull/121…) ensures that keyshares remain consistent and ordered, reducing potential risks during contract execution and resharing. Check out the full repo: github.com/near/mpc 11/ DOCS UPDATE - threshold-signatures What changed: • Added preliminary documentation for communication channels in the MPC protocol. • Moved documentation to the `docs/` folder with a focus on network layer details. • Expanded description of `send_many`, `send_private`, and `echo_broadcast` primitives. • Introduced notation for protocol specifications, particularly for ECDSA. • Added links to notation references in related documentation files. Why it matters: This pull request (github.com/near/threshold-si…) improves the clarity and accessibility of technical documentation for the MPC protocol, aiding developers in understanding communication layer requirements and functionality. Check out the full repo: github.com/near/threshold-si…

Integration of @domaprotocol with @Uniswap V4: Tokenized Domains as Liquid RWAs in AMM Pools Imagine tokenized domains transforming into full fledged assets with yield, integrated directly into Uniswap pools. This would enable the utilization of the domain economy potential, exceeding $340 billion, within DeFi while preserving compatibility with DNS and ICANN requirements. At the core is the Doma SDK. A domain owner, for example, of VVV .com, initiates the tokenization process similar to the command tokenize(VVV .com). The result is an ERC-721 DomainNFT containing the essential metadata: DNS records, expiration date, and a hash for ICANN compliance. Additionally, support for ERC-1155 SubdomainTokens is provided for fractionalization, allowing the domain to be divided into shares corresponding to subdomains. A key advantage, the domain continues to function in its standard mode. DNS remains active, and the website is accessible without interruptions. This approach does not require radical measures, such as destroying a certificate to prove ownership. Uniswap V4 enables the use of custom hooks. We create a Domain/USDC pool with such a hook, which performs three key checks before each swap operation: - Is the domain valid and not approaching its expiration? - Does the registry match the current owner and DNS hash? - Is a higher fee required due to risks, such as an upcoming renewal? If any criterion is not met, the transaction is blocked. This method ensures the reliability of the AMM by preventing trades with invalid assets, although it lacks the spectacle of launching new tokens. Determining the value of a premium .com domain cannot be arbitrary. It is proposed to integrate Chainlink Aggregator to aggregate data from GoDaddy and Sedo auctions, traffic metrics from Google Trends, and historical sales. These data form the TWAP (time weighted average price) for the pool. For lending, LTV limits are set in the range of 50-70% for verified .com domains, which aligns with market data analysis. Special attention is given to scenarios where domain traffic declines or competition arises. The hook monitors the price, if it falls below the established threshold, it initiates startAuction (domainId) in the Doma Marketplace. The DomainNFT is then auctioned, DNS pointers are updated for the new owner, and liquidity provider positions are adjusted. A portion of the fees is directed to Doma Prime vaults to compensate for impermanent loss, ensuring system balance. Liquidity providers receive not only standard swap fees. A share of these fees is allocated to Doma Prime, where domains generate a yield of 5-12% annually. This creates a balanced model. DeFi mechanics are combined with assets that are understandable to marketing and traditional finance specialists. Practical Applications - Domain traders will be able to conduct swap operations directly through the pool, avoiding informal negotiations. - DAO can tokenize brand domains and generate income from their use instead of passive storage. - Startups will have the opportunity to take loans secured by domains while retaining control over the assets. - Communities can fractionalize subdomains using ERC-1155, enabling joint ownership of digital assets. Uniswap V4 will gain a new channel for RWAs with regulatory compliance. Doma will integrate into the DeFi ecosystem as a full fledged layer for domains.

NEAR GITHUB UPDATES [04.09.2025] 📟 What shipped on the @nearprotocol GitHub today? Here’s the latest from the NEAR devs! 1/ NEW RELEASE - near-api-js near-api-js@​6.3.0 What changed: • Introduced `TypedContract` with type-safe ABI support • Added deprecation warnings for functions/classes to be removed in the next major release Why it matters: This release (github.com/near/near-api-js/…) enhances type safety for contract interactions and prepares developers for upcoming breaking changes. Check out the full repo: github.com/near/near-api-js 2/ STATE SYNC UPDATE - nearcore: Compression Followups What changed: • Made state parts compression level configurable, defaulting to `1`. • Added protection against compression bombs. • Stabilized the `StatePartsCompression` feature. • Updated configuration validation for the new compression level parameter. Why it matters: This pull request (github.com/near/nearcore/pul…) optimizes state sync by making compression configurable and ensuring security with anti-bomb measures - developers can now customize compression levels as needed. Check out the full repo: github.com/near/nearcore 3/ OVERFLOW FIX - nearcore What changed: • Replaced `u128` with `U256` in `epoch-manager/src/lib.rs` to prevent overflow when token supply is close to `u128::MAX`. Why it matters: This pull request (github.com/near/nearcore/pul…) prevents critical overflow issues in stake calculations, ensuring stability when token supply approaches the `u128` limit. Check out the full repo: github.com/near/nearcore 4/ FIXED STATE COMPATIBILITY - near-linkdrop What changed: • Resolved state compatibility issues caused by `near_sdk::store` and `near_sdk::collections` not being borsh-compatible. • Updated `Cargo.toml` and `src/lib.rs` to ensure proper functionality. Why it matters: This pull request (github.com/near/near-linkdro…) ensures consistent state handling for linkdrop contracts, preventing potential deployment issues. Check out the full repo: github.com/near/near-linkdro… 5/ CONFIGURATION CHANGE - mpc: Use Configuration Value for `TEE_UPGRADE_PERIOD` What changed: • Replaced constant with configuration value for `TEE_UPGRADE_PERIOD`. • Removed deprecated configuration files. • Updated `lib.rs` to inject `tee_upgrade_period` as an argument. Why it matters: This pull request (github.com/near/mpc/pull/995) allows dynamic configuration for deadlines/timeouts, enabling better testing and support for local attestations. Check out the full repo: github.com/near/mpc 6/ PYTESTS ADDED - mpc What changed: • Added Pytests for CKD • Fixed indexer issue • Added tests for concurrent requests • Added tests for key resharing cancellation • Added tests for contract updates • Added tests for key events Why it matters: This pull request (github.com/near/mpc/pull/985) enhances the testing framework by adding Pytests for CKD and fixing indexer issues - crucial for ensuring code reliability and correctness in the MPC network. Check out the full repo: github.com/near/mpc 7/ DOMAIN SEPARATION - mpc: DomainId Enforcement in Contract What changed: • Added DomainProtocol enforcement in the contract to ensure domain separation. • Updated node and devnet components to support domain separation. • Added new tests to validate domain separation functionality. Why it matters: This pull request (github.com/near/mpc/pull/100…) enforces domain separation in the contract, improving security by preventing cross-domain attacks and ensuring proper isolation between different domains. Check out the full repo: github.com/near/mpc 8/ ROBUST ECDSA SCHEME - threshold-signatures: Passive Security Implementation What changed: • Added presign module for signature pre-computation. • Implemented sign module for final signature generation. • Introduced comprehensive test coverage for end-to-end flows. • Documented the implementation approach in README. Why it matters: This pull request (github.com/near/threshold-si…) enhances security by implementing a robust ECDSA scheme with passive security, optimized for Trusted Execution Environments. Check out the full repo: github.com/near/threshold-si…

NEAR GITHUB UPDATES [27.08.2025] 📟 What shipped on the @nearprotocol GitHub today? Here’s the latest from the NEAR devs! 1/ CONFIGURABLE PV CHECK - nearcore What changed: • Added `protocol_version_check_config_override` configuration option to determine client/network version compatibility. • Default set to `NextNext` epoch to prevent database corruption during missed upgrades. • Validators can set to `Next` to participate in the final compatible epoch. Why it matters: This pull request (github.com/near/nearcore/pul…) enhances node safety by preventing database corruption during protocol upgrades. It provides more flexibility for validators to manage their upgrade cycles. Check out the full repo: github.com/near/nearcore 2/ NEW RELEASE - near-api-js v6.2.6 What changed: • Use `optimistic` finality as the default for RPC queries made from `Account`. • Added an optional `precision` param in the `toDecimal` method to limit digits after the decimal point (rounded down) and included unit tests. Why it matters: This release (github.com/near/near-api-js/…) improves query efficiency by defaulting to `optimistic` finality and adds precision control for decimal conversions, enhancing flexibility in token handling. Check out the full repo: github.com/near/near-api-js 3/ PNPM REPLACEMENT - wallet-selector What changed: • Replaced `yarn` with `pnpm` for faster install times and reduced `node_modules` size. • Updated CI/CD workflows, READMEs, and package.json files to reference `pnpm`. • Added `pnpm-lock.yaml` and `pnpm-workspace.yaml` files to manage dependencies. Why it matters: This pull request (github.com/near/wallet-selec…) improves developer workflow by reducing dependency installation time from ~3 minutes to 20-30 seconds and decreases `node_modules` size from 3.6GB to 2.4GB. Check out the full repo: github.com/near/wallet-selec… 4/ CKD SUPPORT - mpc: Indexer Changes What changed: • Added CKD support to the indexer handler. • Modified `node/src/indexer/handler.rs` for CKD functionality. • Updated `node/src/types.rs` for new types related to CKD. • Adjusted `node/src/tests/mod.rs` to include CKD-related tests. Why it matters: This pull request (github.com/near/mpc/pull/956) introduces CKD support in the indexer, which is essential for secure multi-party threshold signature generation in NEAR's chain abstraction infrastructure. Check out the full repo: github.com/near/mpc 5/ FIX CKDRequest - mpc: Added DomainId What changed: • Added DomainId to CKDRequest in `libs/chain-signatures/contract/src/lib.rs` and `libs/chain-signatures/contract/src/primitives/ckd.rs` • Updated tests in `libs/chain-signatures/contract/tests/ckd.rs` and `libs/chain-signatures/contract/tests/common.rs` Why it matters: This pull request (github.com/near/mpc/pull/955) ensures the CKDRequest structure correctly includes DomainId, which is critical for proper chain abstraction functionality. Check out the full repo: github.com/near/mpc

NEAR GITHUB UPDATES [23.08.2025] 📟 Here’s what the NEAR developers pushed live today. 1/ FIXED OPENAPI SCHEMA - nearcore What changed: • Properly enforced `NonDelegateAction` schema to exclude `DelegateAction`. • Implemented custom `JsonSchema` trait for `NonDelegateAction` to dynamically filter out the `Delegate` variant. • Updated `chain/jsonrpc/openapi/openapi.json` to reflect the correct schema. Why it matters: This pull request (github.com/near/nearcore/pul…) ensures that the OpenAPI spec accurately reflects that `NonDelegateAction` cannot contain a `DelegateAction`, preventing API consumers from making incorrect assumptions. Check out the full repo: github.com/near/nearcore 2/ WASMTIME OPTIMIZATION - nearcore What changed: • Duplicated `VMLogic` and related functionality within `wasmtime_runner` to avoid costly abstraction workarounds. • Made logic internals crate-public to facilitate easier access and modification. • Refactored code to avoid destructing patterns and reintegrated `Config` into `Ctx`. Why it matters: This pull request (github.com/near/nearcore/pul…) enhances performance by reducing abstraction overhead in wasmtime execution, crucial for optimizing runtime efficiency. Check out the full repo: github.com/near/nearcore 3/ TRACING IMPROVEMENTS - nearcore: Chunk Distribution Spans What changed: • Added spans to trace chunk distribution from production to completion. • Introduced new tag `tag_chunk_distribution` for marking these spans. • Converted some spans to the `#​[instrument` format as per style guide. Why it matters: This pull request (github.com/near/nearcore/pul…) enhances observability for chunk distribution, aiding in debugging and performance analysis - particularly useful for developers working on sharding and chunk handling. Check out the full repo: github.com/near/nearcore 4/ INLINING ENABLED - nearcore What changed: • Enabled inlining in Wasmtime runtime configuration. Why it matters: This pull request (github.com/near/nearcore/pul…) introduces inlining to optimize Wasmtime execution, potentially improving performance for smart contract processing. Check out the full repo: github.com/near/nearcore 5/ TEST MIGRATION - near-linkdrop What changed: • Migrated test suite from TypeScript to Rust using `near-sandbox` and `near-api`. • Removed Node.js dependencies and configuration files. • Added comprehensive documentation in `TEST_MIGRATION.md`. • Maintained functional parity with original TypeScript tests. Why it matters: This pull request (github.com/near/near-linkdro…) improves test suite performance and type safety by unifying the development stack in Rust, eliminating Node.js dependencies. Check out the full repo: github.com/near/near-linkdro… 6/ ADD DOMAINID TO CKDREQUEST - mpc What changed: • Added `domain_id` field to `CKDRequest` to identify the master key used for derivation. • Updated README to include the new `domain_id` parameter in the request example. Why it matters: This pull request (github.com/near/mpc/pull/934) enhances the chain key derivation process by allowing specification of a master key through `domain_id`, improving flexibility for secure multi-party computations. Check out the full repo: github.com/near/mpc 7/ TEST UPDATE - near/mpc: TEE Attestation Validation Test What changed: • Added integration test for `submit_participant_info` with valid TEE attestation. • Consolidated test utilities into a dedicated `test_utils` module within the attestation crate. • Refactored existing code to use the new shared test utilities. • Fixed a bug in the `get_docker_compose_hash` function related to outdated YAML. Why it matters: This pull request (github.com/near/mpc/pull/828) ensures that the contract properly validates TEE attestations, improving the security and reliability of MPC node participation. Check out the full repo: github.com/near/mpc 8/ OPERATOR GUIDE - mpc: First Version of TEE Node Operator Guide What changed: • Added a comprehensive guide for deploying a self-hosted MPC node using Intel TDX. • Detailed hardware, software, and TDX setup prerequisites. • Provided step-by-step instructions for MPC node deployment, key retrieval, and joining the MPC cluster. • Added troubleshooting section and transition phase details. • Linked TBD items to relevant GitHub issues for future updates. Why it matters: This pull request (github.com/near/mpc/pull/886) provides a detailed operator guide for deploying TEE-based MPC nodes, aiding operators in setting up secure, isolated nodes - essential for maintaining the integrity of the MPC network. Check out the full repo: github.com/near/mpc

PermissionedDEX (XLS-81) is here, bringing KYC'd trading with DomainID! OfferCreate mods boost compliance but watch out for invalid domains. Vote data pending. How does this impact compliant #DeFi to you? #XRPL #Blockchain #Ripple [Source: github.com/XRPLF/XRPL-Standa…

PermissionedDEX (XLS-81) introduces KYC’d trading with DomainID and lsfHybrid flags in Offer objects! OfferCreate mods ensure domain-specific fills, failing on invalid domains. Pending vote data. Who’s building compliant DEXes? #XRPL #Blockchain #DeFi [Source: github.com/

PermissionedDEX (XLS-81) brings KYC’d trading with DomainID! Modified OfferCreate with lsfHybrid flags ensures domain-specific filling. It fails on invalid domains, keeping it compliant! Pending vote data. What's your take? #XRPL #Blockchain [Source: github.com/XRPLF/XRPL

PermissionedDEX (XLS-81) introduces KYC trading with DomainID & lsfHybrid flags in Offers! OfferCreate mods ensure compliance. Pending vote data, but this is HUGE for institutions! Who's ready to bridge TradFi & DeFi? #XRPL #DeFi #Blockchain #Ripple [Source: github.com/

A client's ADFS went down this morning. Keep these commands for emergency cutover. (PW Sync must be enabled prior to this) Connect-MgGraph -Scopes "Domain.ReadWrite.All","Directory.AccessAsUser.All" Update-MgDomain -DomainId contoso.com -AuthenticationType "Managed"

🚨 Last Call! Webinar GRATIS E-sertifikat dari Rumahweb x PANDI mulai sebentar lagi! ⏰ Masih bisa daftar sekarang 👉 rwb.pw/jagadomain 📅 Rabu, 25 Juni 2025 🕒 15.00 WIB – via Zoom Topik: Cara jaga domain sebagai aset digital & hindari sengketa ⚖️ Jangan sampai ketinggalan! 🛡️ #Rumahweb #NaikLevel #WebinarBisnis #KeamananDomain #DomainID

📢 GRATIS & dapat e-sertifikat! Domain itu Aset Digital yang penting buat bisnismu! Pelajari cara menjaga dan terhindar dari sengketa domain. Yuk ikut Webinar Rumahweb x PANDI 🛡️ 🗓️ Rabu, 25 Juni 2025 🕒 15.00 WIB – via Zoom 📌 Daftar sekarang 👉 rwb.pw/jagadomain Kupas tuntas soal domain sebagai aset digital & cara mengamankannya dari masalah hukum 💡 #Rumahweb #NaikLevel #WebinarBisnis #KeamananDomain #DomainID

Kenapa harus domain .id? Selain menunjukkan identitas nasional, domain .id juga lebih SEO friendly dan mudah diingat loh wargibumi ! , yuk berlangganan dengan kami ! solusiwebhoster.co.id . #domainid #vsdomaincom #seo