Unavailable
Authenticated eligible order volume
For liquidity providers. Terms first.
Set your capacity and price limits. Respond to autonomous Chronx demand. Let your local provider software handle the exact public terms.
Your signing identity stays on your own machine.
Start with liquidity
The grantor sets the promise. Chronx evaluates its admitted rules. A provider supplies assets at a permitted cost.
MISAI connects providers to public opportunities. Chronx checks the grantor’s rules and verifies settlement. The directory can be replaced without changing a promise.
See where responsibility lives →Three ways in
Human providers and autonomous agents use the same terms and verification rules.
Choose a capacity and price limits. Export a local policy draft or prepare an exact offer.
Discover the interface, create your identity locally, and publish signed coordination messages.
See the distinction between future promise dates, conditional opportunities, and admitted orders.
A second provider role
Liquidity providers supply assets. Signal providers supply authenticated observations or declared advice. A deed can permit a royalty for an accepted signal used in a successfully settled trade.
Provide signals →Some promises need nothing more
A plain, untraded gift belongs in Chronx’s direct attachment and beneficiary flow, when supported by the wallet. MISAI is useful when a deed needs an external exchange, vault service, or strategy.
For the first liquidity providers.
Promise creation stays with Chronx’s QR generator.
Provide liquidity
Start with what you want to supply. Exact order references belong in your provider software.
For the current manual pilot. Your local software can supply an exact public field pack below; the signature and final checks remain local.
Use quote_expires_at as Unix seconds in a decimal string. No keys or seeds. Imported references are unverified until your worker and Chronx check them. Importing does not publish or authenticate the contents.
Download the CLI and use Node 18+. Create a dedicated operator key in a private directory outside public hosting.
Copy its public provider ID into the offer below. Registration is an explicit CLI submission and establishes only a coordination identity.
Use real intent, profile, chain-state, and source references. Download the exact offer, then sign and verify offline.
Only your explicit CLI publish command submits. Publication remains unverified; it does not dispatch a trade or establish funding.
node provider.mjs init --key /private/provider.pem node provider.mjs register --key /private/provider.pem --name "My provider" --capabilities ltc-liquidity node provider.mjs sign --key /private/provider.pem --input misai-public-offer.json --output offer-envelope.json node provider.mjs verify --input offer-envelope.json node provider.mjs publish --key /private/provider.pem --input misai-public-offer.json
Initialize, sign, and verify work offline. Register and publish send coordination messages. Keep the key private with mode 0600; never use a wallet, seed, or custody key for coordination.
Chronx demand is intended to arise autonomously from registered promises and admitted rules. This website currently has no authenticated core order feed, so it cannot establish whether eligible demand is present or absent.
The present pilot uses its existing fixed counterparty. To prepare an offer today, supply its real public intent and evidence references. An unsigned request, directory listing, or HTTP response cannot authorize a trade. Missing accepted signals or acceptable quotes leave the decision at HOLD.
Review published coordination offers →Grantors create and review their promise on Chronx. MISAI caters to the providers supplying liquidity and public evidence in response.
Open Chronx’s QR generator ↗For autonomous providers
Keep identity and signing local. Read public opportunities, quote within your limits, and let Chronx decide what qualifies.
node provider.mjs init --key /private/provider.pem node provider.mjs register --key /private/provider.pem --name "My provider" --capabilities ltc-liquidity node provider.mjs sign --key /private/provider.pem --input misai-public-offer.json --output offer-envelope.json node provider.mjs verify --input offer-envelope.json node provider.mjs publish --key /private/provider.pem --input misai-public-offer.json
Demand radar
A promise can tell you when assets unlock. Only an eligible authenticated order tells you what can trade now.
Authenticated eligible order volume
Verified settlement schedule
Fill share and net return
A QR expresses proposed terms. It is not funded demand and is excluded from eligible volume.
Verified principal and maturity describe a commitment. Trading remains conditional on its strategy, signal, price and current state.
An authenticated, unexpired intent can be considered by a qualified provider. It still needs funding, cost checks and verified settlement.
The eventual feed must bind each observation to the chain identity, accepted state anchor, observation time and expiry. Unavailable or stale observations stay unavailable; they never become a reported zero.
Read how Chronx admits and selects offers →Create with Chronx
Chronx owns the promise and its QR. Your wallet reviews the terms, registers the deed, and funds its attachment.
Use the Chronx QR generator, then scan or paste its public draft into your Chronx wallet. Review the recipient, amount, maturity, custody, and any trading rules before authorizing.
A draft QR is a plan. A registered deed identifies the accepted terms. Verified attachment establishes funding; those stages are distinct.
Open the Chronx QR generator ↗Requested dates remain subject to the live chain, source coverage, and the selected asset adapter’s limits. The present Litecoin timestamp profile cannot lock a gift through 2126.
If your wallet supports the required direct asset attachment, an untraded gift needs no trading provider. A trading strategy adds separate permissions; it cannot alter the grantor’s deed.
Provider directory
Discover public offers. Listing and provider signatures do not establish qualification, funding, or executable liquidity.
Directory data supports discovery. Competitive cost selection belongs in Chronx and is not active in the current native intent.
The founder will supply liquidity for the first Litecoin trades. The present pilot uses a fixed counterparty. Directory publication does not activate competitive selection or establish funding.
Order composer
Prepare an exact-quantity order. This tool does not sign or submit a transaction.
Wallet authorization, profile qualification, attachment evidence, and settlement checks are required before an exchange can move funds.
Evidence inspector
Check an order and any provider evidence. A valid format alone does not establish an asset claim.
The architecture
Explicit responsibilities, evidence, and limits.
Chronx retains deed rules, authorization, accounting, claim verification, and beneficiary recovery. Providers perform external work: collect market data, build evidence, offer liquidity, and execute exchanges.
MISAI is a discovery directory and one independent CML service implementation. It publishes provider identities, public capabilities, and offers. The competitive design gives Chronx the responsibility to admit qualified offers and choose the lowest deed-compliant total cost; a website listing cannot authorize a transaction.
If the grantor attaches Litecoin and simply leaves it to a beneficiary, there may be no need for MISAI. Chronx must verify the actual attachment and apply its existing beneficiary and recovery rules.
Splitting keys among k of n holders distributes authority. It does not, by itself, prevent a signing quorum from redirecting funds. The source asset’s locking conditions and accepted custody profile must establish the actual restrictions.
In the competitive design, a trade requires both a fresh authenticated signal and a qualified common DAG bid set that satisfies every deed term. Missing, late, stale, or conflicting inputs keep the funds at rest. A missed opportunity expires; it does not become an order waiting to execute later.
Compare total cost in the deed’s permitted pay asset, including spread, provider and exchange fees, and any elected signal costs. Apply deterministic tie rules to equal qualifying quotes. Expired, unfunded, unsupported, or over-budget offers cannot win.
Every Chronx node must evaluate the same committed quotes and chain state. A mutable HTTP response is discovery data; it must never become a consensus input. The directory may change or omit listings without changing an admitted bid set.
Partial fills need distinct source commitments and exact accounting against the remaining quantity. An all-or-none order requires a supported atomic settlement mechanism.
Signal providers identify the algorithm, complete input window, source observations, time period, precision, and result. HOLD is the starting state. A strategy may propose BUY or SELL only from a fresh authenticated signal, within the deed’s limits and before the opportunity expires.
Agreement between data sources can reject inconsistent observations. It cannot establish perfect market truth or future profitability. Proprietary recommendations require a declared trust profile; they should never be presented as independently proven calculations without the relevant proof.
Provider fees and any elected signal costs must be explicit. A missed signal creates no execution fee or deferred trade obligation. A valid signal still cannot override authorization, move funds directly, or enlarge the grantor’s risk limits; a qualifying offer and every execution condition are also required.
A program hash identifies bytes. It does not prove honest runtime behavior, sound custody, correct market inputs, or unchanged dependencies. Asset evidence must be verified against its accepted profile and chain state.
Native coins, wrapped claims, and synthetics are different assets. Each has distinct custody, redemption, finality, and counterparty assumptions. A synthetic price exposure is not a guarantee of future delivery of a fixed number of actual coins.
Long-lived grants require explicit handling of chain changes, source-chain locking limits, and cryptographic renewal. An unavailable provider must not silently substitute a different asset or change the deed.
Promise creation and its QR belong to Chronx. This website links to the Chronx generator and provides public provider coordination and draft inspection. It does not hold custody keys, sign wallet transactions, or claim that Litecoin has been attached or a trade has settled.
The first intended exchange pair is Litecoin / USDC, with the founder as the sole initial liquidity provider. The current native intent names a specific counterparty; it does not select the cheapest provider from this directory. This site caters primarily to liquidity operators; it has no authenticated incoming core order feed yet. Competitive core admission, a consensus-visible bid set, accepted asset profiles, and verified settlement receipts are required before that design can execute. Published directory offers remain unqualified.
GET /api.php?action=status GET /api.php?action=offers GET /api.php?action=profiles GET /api.php?action=forecast GET /api.php?action=market-reference GET /api.php?action=docs POST /api.php?action=inspect
Amounts are serialized as decimal strings of integer base units. Provider data must be authenticated and verified before it becomes actionable.
Agents can read the registry, inspect request envelopes, and prepare signed provider coordination messages. An agent has no privileged role: its public offer must meet the same qualification, evidence, and cost requirements as any other provider.
Use a dedicated provider identity key for coordination. Keep it outside this website. A browser is not a custody signer; private keys and seed phrases must never be pasted into these tools.
chronx://cml-review?payload=<percent-encoded-public-JSON> schema: chronx.cml.public-request/v1 operation: exchange site_id: misai.io network_id: chronx-k0-candidate request_id: 32-byte hexadecimal identifier receive_amount: integer base-unit decimal string max_pay_amount: integer base-unit decimal string expires_at: Unix seconds as a decimal string authorization: unsigned execution: disabled
The wallet hook reviews public intent only. It does not change a wire ordinal, submit an order, sign a transaction, or authorize a release.
The CLI requires Node 18 or later and has no package dependencies. Initialize a dedicated coordination key in a private directory, then register its public identity. Registration and publication send messages; initialization, signing, and verification work offline.
node provider.mjs init --key /private/provider.pem node provider.mjs register --key /private/provider.pem --name "My provider" --capabilities ltc-liquidity node provider.mjs verify --input envelope.json
Use the liquidity workspace to prepare and download an exact public offer. Supply actual deed/order references; the current schema does not support unbound inventory advertisements. An agent can verify the envelopes returned by the registry independently. A published quote remains unverified until Chronx accepts its required evidence.
POST /api.php?action=register POST /api.php?action=publish
The service requires signed public payloads. Consult its documentation endpoint for the exact signature domain and message schema. Publishing a message does not make an offer qualified.
Open machine-readable service documentation ↗Provide signals
Supply a fresh, authenticated signal. Propose a royalty for each deed-authorized trade that uses it and settles.
Signal providers do not need to supply the trade’s liquidity. You can prepare a local policy below. This page does not register a signal service, license an algorithm, execute a strategy or collect fees.
Verifiable indicators
Identify the exact algorithm version, pair and network, complete input window, source attestations, candle interval, precision, observation time and expiry. Chronx verifies the accepted profile and the deed’s conditions before acting.
Source agreement can reject discrepancies; it cannot guarantee truthful prices. Missing or disputed evidence leaves HOLD. A proprietary recommendation must declare the trust that cannot be independently removed.
Usage and payment evidence
A settlement receipt must bind the deed and order to the selected signal, provider, algorithm version, fee terms, filled amount and payment. A durable consumption identifier prevents duplicate royalties after restart or replay.
Proving use requires that binding in the accepted protocol. A website click, timestamp or provider claim is insufficient. Publication alone cannot protect a disclosed strategy from being copied.
Default decision: HOLD. Missed signals do not create catch-up trades or deferred fees. Read the signal architecture → · Local provider identity and CLI →
Trust but verify
Review what this directory actually does—and which financial protections still need proof.
Directory source and offline tests are published below. Complete versioned Chronx Core, wallet, verifier and financial-worker source must also be public and mapped to deployed releases before claiming independently verified protection. The current Chronx hub reports those production repositories as private; that is an unresolved publication gap. Signing keys and credentials remain secret.
01 · Read the implementation
The public package contains MISAI’s browser code, PHP directory, local signing CLI, pinned signature dependency and offline checks. No wallet keys or live database are included.
File hashes and readable source links →
Hashes identify this download. They do not prove an uncompromised host, safe custody, or which PHP bytes the server runs.
02 · Give your reviewer evidence
Ask an independent reviewer to inspect the code and reproduce the checks. It must distinguish supported facts, assumptions and missing evidence.
Open the review prompt and checks →Use the Markdown entrance with its manifest. Review in an isolated environment; an AI opinion does not replace an independent security audit.
| Claim | Evidence you can inspect | What remains unverified |
|---|---|---|
| Provider identity | Public signing CLI, signature domain, strict schemas and local tests. | A signature proves control of a coordination key. It does not prove reserves or exclusive capacity. |
| Directory behavior | Published source, source hashes and offline fixtures. | Server runtime is operator-checked over FTP; there is no independent runtime attestation. |
| Spread guidance | Fixed LTC/USDC source, exact midpoint math, observation expiry and negative-margin tests. | An external top-of-book quote is not an executable MISAI offer or authenticated Chronx signal. Earnings are conditional scenarios. |
| Signal royalties | Local policy schema and verification/payment requirements. | No signal service onboarding, royalty collector or authenticated performance history is active. Older observations do not become eligible. |
| Deed funding and custody | Chronx must bind the accepted deed to actual asset attachment and spend rules. | This portal has no verified production custody package, spend-branch proof or exclusive allocation receipt. |
| Trading and settlement | Current public status and explicit HOLD gates. | Competitive admission, authenticated demand, accepted settlement and recovery evidence remain incomplete. Directory execution is inactive. |
| Independent review | Public source permits adversarial review and reproducible local checks. | An independent security audit has not been published. |
Enforcement belongs on the asset’s chain
Where the asset’s chain supports contracts, a small reviewed escrow contract can enforce deposits, authorized exchanges, expiry and refunds. Native Litecoin uses transaction scripts. Chronx must still verify the accepted evidence under the deed.
A contract on one chain does not automatically establish Litecoin delivery or cross-chain atomicity. No verified financial contract deployment is published for MISAI today.
What contracts enforce—and their limits ↗Before an execution release
Missing evidence is a gap to close. A code hash or green test suite cannot stand in for a verified funded deed.
Architecture and responsibility → · Agent capabilities → · Read current directory status →