Sources and verification
Juris contract queries provide pool settings, margin positions, staking information and vault inventory. The technical reference documents the message formats and the implementation versions listed below.
Read contract data
Section titled “Read contract data”Use the factory to discover pools and liquidation queues. Query individual contracts for their current settings and balances. Queries and data types covers JSON message formats, amounts and asset identifiers.
Configuration values can change. The deployment reference includes observations dated September 22, 2026. Those observations were not pinned to a block height and are not a live parameter feed.
Source access
Section titled “Source access”The implementation repositories are private and require repository access. The links below identify the versions used for the technical reference.
These versions have not been matched to deployed Wasm checksums or to the current LSF preview build. Contract configuration, migration authority and source version are separate parts of an integration’s deployment information.
Transactions and balances
Section titled “Transactions and balances”A submitted wallet request becomes a completed action only after successful execution. Use the transaction result and refreshed contract balances to check a deposit, repayment, reward claim or redemption.
For troubleshooting, retain the chain, public transaction hash and error message. Never share a seed phrase or private key. See Troubleshooting.
Programme terms
Section titled “Programme terms”The Shirini Promotion has its own dates, eligible-revenue definition and snapshot rules. Its allocation percentages describe the programme; they are not a record of completed payments.
Security and administrative controls describes the permissions affecting the protocol. No audit report or source-to-binary certification is provided with this reference.
Token and market records
Section titled “Token and market records”Token addresses, Markets & listings and Bridge JURIS use one versioned catalogue. Its public JSON snapshot includes source links and observation dates.
Token identity is checked against contract metadata, bridge origin mappings and network registries. Project deprecation decisions are recorded separately from whether a contract still exists. Trading, deposits, withdrawals and each bridge direction have separate statuses; an unverified operation is not marked available.
Exchange notices establish listing and delisting dates. Pool records identify assets and contracts; indexer activity does not guarantee an executable quote. Historical GitBook entries are discovery leads, not current operational evidence.
These docs maintain the project’s published token reference. Contract state and provider notices remain the evidence for on-chain behavior and exchange operations.