Standards & Taxation ​

All smart contracts deployed in Juvantia must adhere to the following technical and economic standards.

1. Currency Standard ​

• Permitted Tokens: Only Verified Currencies (Whitelisted MiCA-compliant stablecoins).
• Requirement: Contracts must accept ONLY Verified Currencies for payments. Usage of unverified tokens or native coin (ETH) for goods/services is prohibited.

2. Taxation (Withholding) ​

Commercial contracts must automatically calculate and withhold taxes per transaction. The tax is sent to the Treasury Contract immediately.

Implementation Note ​

The contract must deduct the tax from the msg.value (or JVD transfer amount) before sending the remainder to the seller/provider.

3. Compliance & Fines ​

To ensure legal compliance, every contract must be "Fineable".

• Custodia Contract: 0xjdbv3Jbd...... (Placeholder)
• Mechanism: The Custodia contract has the authority to request a fine deduction from a target contract's balance or a user's locked funds within that contract.
• Check: Before executing a withdrawal or high-value transfer, the contract SHOULD check if the user has outstanding fines in the Custodia system (optional but recommended to avoid transaction reversal).

4. Security & Verification (Recommended) ​

To ensure the safety of Juvantia's digital infrastructure, the following are highly recommended:

• Source Code Verification: All contract code must be verified and published on the Juvantia Explorer.
• Owner Registry: The contract owner address must be linked to a registered Civis.
• Emergency Stop: Contracts holding significant funds should implement a pause() functionality accessible by the owner (and potentially Custodia in extreme emergencies).
• Events: Emit standard events (e.g., TaxPaid, FineDeducted) for transparency.

5. Sub-Asset Factory & Hierarchical Tokens ​

For composite assets such as multi-unit buildings (Domus) comprising individual apartments or modules (Cella), the smart contract layer implements an on-chain parent-child hierarchy in JuvantiaAssetFabrica:

• Sub-Asset Creation: Deployed via createSubAsset(parentAssetId, assetId, name, symbol, initialOwner).
• State Indexing: The factory stores mappings parentAsset[clone] => parent and _subAssets[parent] => clone[].
• Token Identifier Standard: Parent structures use base identifiers (e.g. DM-3553), while constituent sub-assets append sequential suffixes (e.g. DM-3553-C1, DM-3553-C2).
• Economic Isolation: Each sub-asset token contract is a distinct EIP-1167 clone with an independent 100,000 APU supply. Revenue routing in JuvantiaRevenueDistributor guarantees that private leasing yields accrue strictly to sub-asset holders rather than dissolving across the parent building.