Environment My Sovereign Network / Pilot Sandbox · SGLD · config v0.8

SANDBOX / PILOT

Saved to this browser · {{ savedAt }} Load configuration

Layout

Pilot template

Mock template for future pilots. Not a live chain. The Domain is the sovereign domain currency. Hubs and annexes stay on that domain. Every Domain, Hub, and Annex uses the JIL L1 rail. Every transaction runs through ATCE. Corridor transactions require gas ignition. A global corridor also includes InterOp.

Your sovereign pilot environment

{{ ready.done }} / {{ ready.total }}modules configured

Progress derives from saved configuration in this session.

What needs attention

All prerequisites satisfied.

Recent pilot activity

Configuration truth model · per module

Module

Draft

Validated

Approved

Desired

Observed

Health

An accepted request is not a completed deployment. Observed and health columns read from provisioning and telemetry, shown here as synthetic sandbox values.

Prerequisite

Module

State

Owner

Launch readiness

{{ ready.done }} / {{ ready.total }}

{{ ready.remaining }} prerequisites require attention before provisioning can be requested.

Hierarchy explorer{{ treeStats }}

Add node

Structure canvas

The Domain is this sovereign domain's own digital currency. Hubs and annexes are tied to that domain, the way other assets sit on Ethereum. They do not travel a corridor. The tree is not capped by the UI; limits are server-enforced.

Node inspector

Internal ID{{ insp.id }} Type{{ insp.typeName }} Parent{{ insp.parent }} Ledger scope{{ insp.scope }} TokenSGLD (inherited) Status{{ insp.status }} Revision{{ insp.rev }}

Display name

Move / reassign annex

Impact preview: {{ insp.preview }}

Historical paths

Fail-closed · no transaction reaches finalization without an explicit APPROVED decision

{{ sv.name }}● {{ sv.health }}

:{{ sv.port }} · {{ sv.tech }}

{{ sv.topics }}

Simulate outages (sandbox)

/health cascade · compliance-api

Failure

Behavior

Recovery

If the system cannot determine risk, the transaction is held until compliance can be verified. Bypass is not configurable in any environment.

Pilot

Zone

Regulator

Review / Block

State

{{ z.id }}

{{ z.rb }}

Zone policy · {{ cZ.reg }}

{{ cZ.id }} · {{ cZ.jur }}

GENESIS is the JIL base layer every zone inherits from. It is read-only in the pilot.

Travel rule{{ cZ.travel }}

All zones inherit from GENESIS; zone values override GENESIS and pilot overrides take precedence over both. Zone rows in this template are mock sample values. They are not a live chain.

{{ p.effW }}base {{ p.w }}%

Normalized score (0-100) for test address

Composite score

{{ cScore.formula }}

0 · ApproveReview ≥ {{ cScore.rev }} · Block ≥ {{ cScore.blk }} ({{ cScore.zone }})100

Provider resilience

CacheRedis · 5-minute TTL · key: provider + address + chain Circuit breaker opens after5 consecutive failures Reset timeout30 s, then one half-open probe Timeout per provider call10 s Two providers downRemaining provider 100% + caution flag All three downInternal screening only (sanctions, velocity)

List

Source

Refresh

Last refreshed

Scheduled daily at 02:00 UTC. Diffs trigger re-screening of active addresses.

Screening points · required

{{ p.n }}{{ p.label }} · {{ p.desc }}Always on

Matching configuration

Addresses: exact match (case-insensitive hex, case-sensitive base58).

Fuzzy block threshold (%)

Partial / review floor (%)

Test entity-name similarity: {{ cSim }}%

Outcome: {{ cSimOut.decision }} {{ cSimOut.why }}

Internal watchlist · real-time{{ cWatchCount }}

Synthetic transaction

Zone

Asset

Counterparty address

Amount (USD equiv.)

Best name-match vs lists (%)

Tx count, last hour

USD volume, last hour

BID threshold (USD)

Provider scores and availability come from the Risk scoring and Pipeline tabs.

compliance-api decision

Check

Result

Effect

{{ r.check }}

Appends to compliance_decisions and jil.compliance.decisions.

Decision ID

Type

Zone

Score

Decision

{{ d.short }}

Resolved

Decision record · append-only

{{ cDecJson }}

Overrides create a new record referencing the original. Retention 10 years; daily Merkle root anchored to the JIL L1; ISO 20022 export.

ATCE vesting preview, patent pending. Vesting sell limits are not a current product of JIL Sovereign Technologies Incorporated. This tab previews that filed design. It is not the transaction gate. Every transaction on a pilot still runs through ATCE, and there is no path around that gate.

Tier

Unlock % of vested

Window (days)

Daily sell limit %

Tier {{ t.n }}

Evaluate a sell

Vested allocation

Sold today (UTC)

Requested sell

Tier {{ u.n }} unlockeddayof window

ATCE evaluation (preview)

Window

Unlocked

Daily allowance

State

Tier {{ r.n }}

Total

Remaining {{ aRes.remain }}

Windows run in parallel; daily totals reset at midnight UTC.

{{ l.t }}req {{ l.req }} · allowed {{ l.allowed }}{{ l.decision }}

State tables: atce_unlock_events (address, tier, amount, unlock and window-end timestamps) · atce_daily_sales (per address, day and window) · atce_decisions (requested, allowed, decision, reasons).

validators

Placement status

{{ valDone }} / 10

Approval state: {{ valSaved }} · Pilot host: a company host

JIL owns and controls all ten validator processes per L1. You choose preferred hosting regions and providers; these are preferences subject to JIL approval and availability. You cannot start, stop, sign for or rotate validators.

Slot

Region

Preferred host (production)

Actual host (pilot, from telemetry)

Health

Validator {{ s.num }}

Healthy · {{ s.seen }}

Connection catalog{{ connCount }} selected

Connector names are mock template data. A future pilot replaces this list from its own connector registry.

Execution & routing preferences

Execution venue

Routing policy mode

Preferred transit L1

Fee ceiling (USD)

Route comparator

USD → AED · Source: SGLD pilot → Destination: external L1 · hypothetical rates

Estimated total

Active route under policy: {{ activeRoute }}

Quote {{ quote.id }} · {{ quote.route }} · {{ quote.total }} · valid 15 min (illustrative) · approval state: {{ routeApproval }}

InterOp currency bridge establishment: $25,000 indicative, negotiable. This is not a fee for creating a sovereign L1. All other fees TBD. The dollar figures on this screen are mock template data. Corridor transactions, global and domestic, require gas ignition. The capacity lease is not published. A global corridor runs through ATCE and includes InterOp.

Token specification · example only

Sovereign domainSGLD (Domain) Symbol Peg / reference

Permitted scopesHubs and annexes tied to this domain

Issuance & redemption (sandbox)

Sandbox supply: {{ scSupply }}

Stablecoin issuance is a separate regulated capability. Registration, issuance and processing fees: TBD.

Scope

Tx hash

Token

Block

Hops

Cost

Status

{{ t.hash }}

SGLD

TBD

Transaction detail

{{ txD.hash }}

Recorded as{{ txD.scope }} Level{{ txD.clsName }} Block{{ txD.block }} Finality{{ txD.fin }} Policy{{ txD.policy }} Route{{ txD.route }}

Events

Select a transaction to see finality, policy decision and events.

Hubs and annexes stay on this sovereign domain. These rows are mock template data.

User

Role

MFA

Status

{{ u.role }}

Invite by email

Role

Effective permissions · server-enforced

Capability

Admin

Operator

Viewer

Validator lifecycle, signing keys and treasury operations remain JIL-only for every customer role.

Time

Actor

Module

Action

Before → after

Outcome

Every change you make in this prototype is appended here. In production the log is immutable and server-side.

Choose the levels to test or deploy. The Domain is included whenever you choose a hub or an annex. An annex that sits on a hub also includes that hub.

Test does not write a deployment. Deploy writes the selected levels only when the auditor passes. The node is not started and no height is read.

Domain Hub Annex

The chain watcher for this demonstration is the public explorer on this host.

/scan.html

What this studio is

This is a demonstration studio. It does not name a customer. The rows are sample data. Production access uses enterprise SSO and MFA. This page does not publish a sign-in.

The rows, quotes, users, zones, and heights are sample data stored in this browser. This host does not read a live chain and does not publish a block height. Save configuration writes to this browser. Load configuration reads that same browser store. Nothing on this host signs, issues, or moves value.

pilot.jilsovereign.net is a different page and stays that way. The public apex does not serve this studio. The service refuses to start as production.

The sample domain

The template opens on one sovereign domain, SGLD, Sovereign Gold Domain. SGLD is the Domain. The Domain is that domain's own digital currency. In the tree it is node n01, status Configured, revision v0.8. SGLD is the shared sample in this template, not a live book of record.

Hubs and annexes are tied to that domain, the way other assets sit on Ethereum. They are not a second currency, and they do not travel a corridor. The sample hub ledgers under SGLD are Settlement 52, Wholesale 17, and Ledger 99. Ledger 99 is still Draft. The sample annexes under a hub ledger are Treasury Annex and Clearing Annex under Settlement 52, and Custody Annex under Wholesale 17. Those annexes stay on the domain.

Direct Annex, code AD, node n08, is an annex whose parent is the Domain. That is the direct annex.

The tree is not capped by this screen. You can add a hub or annex shell node, rename a node without changing its internal ID, and move an annex to another eligible parent. Validate tree checks the shape. Export JSON downloads the tree as it sits in this browser. Limits that matter in a real pilot are enforced by the server, not by how many rows the screen will draw.

Two kinds of movement

Inside the domain. A transaction with no corridor hop stays on the sovereign domain. The Domain, hubs, and an annex that sits under a hub all stay there. On the Transactions screen a row with zero hops is labeled as inside the domain. It still runs through ATCE. There is no path around ATCE, including for a transaction that never leaves the domain.

On a corridor. A corridor is movement between sovereign domains. The rail on every path is JIL L1. Every corridor transaction, global and domestic, requires gas ignition. A global corridor runs through ATCE and also includes InterOp. A domestic corridor still requires gas ignition and still runs through ATCE. InterOp is the extra service on the global corridor.

Gas ignition is required before corridor settlement. The capacity lease is not published. Do not read the dollar figures on InterOp as that lease. Those figures are mock.

The gate

Every transaction runs through ATCE. If the system cannot determine risk, the transaction is held until compliance can be verified. Bypass is not a setting. It is not available in this template and it is not available in a later production environment.

The Compliance and ATCE screen is where a pilot drafts zone policy. The sample zones carry a regulator, a review threshold, and a block threshold. A zone draft is not in force until it is published, and the cockpit does not mark Compliance zones complete until the drafts are published and a decision test has been recorded. Decisions you will see in the sample are APPROVED, FLAG, REVIEW, and BLOCKED. REVIEW is held. BLOCKED does not finalize.

The same screen can simulate an outage of a compliance dependency. That switch is sandbox only. Restoring the services returns the cascade to the sample healthy state. Use it to see a hold. Do not treat the simulated outage as a live incident.

The ATCE tab also includes a patent-pending preview of vesting sell limits. That preview is not the transaction gate. Vesting sell limits are not a current product. The gate is the rule above: every transaction runs through ATCE, and there is no path around it.

How the cockpit keeps score

Overview counts eight modules. A module shows Complete only when its own rule is met in the saved configuration. Attention means the rule is not met yet. The next action on the cockpit points at the first module that is not complete.

Network identity. Owned by JIL. The sample is already the SGLD pilot sandbox, created from this template.
Domain/Hub/Annex tree. Owned by the customer. Complete when every hub and annex node is configured. Ledger 99, Clearing Annex, and Custody Annex still need setup in the sample.
Compliance zones. Customer prepares, JIL takes the publish. Complete when no zone draft is unpublished and at least one decision test is recorded.
Validators. Customer prepares, JIL approves. Complete when all ten slots have a placement and the set has been submitted.
InterOp connectors. Owned by the customer. Complete when at least one connector from the catalog is selected.
Route policy. Customer prepares, JIL approves. Complete when a route quote has been submitted for approval.
Users and roles. Owned by the customer. Complete when the list includes an approver, not only an operator.
Stablecoin registration. Owned by the customer. Complete once registration has moved past the first step. Issuance itself stays a separate gate.

The Lifecycle tab is the configuration truth model for each module: Draft, Validated, Approved, then Desired, Observed, and Health. An accepted request is not a completed deployment. Observed and Health on this host are synthetic sandbox values. They are not telemetry from a live fleet.

The Checklist tab is the same eight modules as launch readiness. Provisioning is not requested from a red checklist. Open on a row jumps to that module's screen.

Validators

There are ten slots, spread across Europe, the Americas, Asia, and Middle East and Africa in the sample. JIL owns and runs all ten validator processes for the L1. You choose a preferred region and a preferred production host. Those choices are preferences. They wait on JIL approval and on capacity.

In this template the actual pilot host is a company host. You cannot start a validator, stop one, sign for one, or rotate a key. The permission table marks start, stop, and rotate as denied for every customer role. Signing keys and treasury operations are denied the same way. Save and submit placements records the preference set. It does not bring a validator up.

InterOp and corridors

The connection catalog is mock. Connector names in this template are sample names. A future pilot replaces the list from its own connector registry. Select at least one before the cockpit will mark connectors complete.

Execution and routing is where you set the venue, the routing policy mode, the preferred transit L1, and a fee ceiling. The route comparator is a hypothetical comparison, in the sample a USD to AED path from the SGLD pilot toward an external L1. Request quote and Submit for approval record that sample quote. A quote on this screen is illustrative. The sample says it is valid for 15 minutes and that is part of the mock, not a live market.

The currency-bridge line of $25,000 is an indicative mock figure. It is negotiable in the story of the template. It is not a fee for creating a sovereign L1. Every other fee on the screen is still to be determined. Corridor transactions, global and domestic, require gas ignition. The capacity lease is not published.

A global corridor is the path that includes InterOp on top of ATCE. Choosing a connector and submitting a route does not open that corridor. It records the pilot's request.

Stablecoins

A stablecoin in this template is specified on the Domain, SGLD. The sample peg choices are USD, EUR, and AED. Permitted scopes are hubs and annexes tied to this domain. That means the stablecoin is an asset on the domain.

Registration is five steps: Define, Register, Reserves, Approve, Activate. Each step has its own evidence line, and the advance button records the step in this browser. Approve and Activate are dual-control shaped, and the sign-off in the sample is synthetic. Issue test amount and Redeem move a sandbox supply only.

Stablecoin issuance is a separate regulated capability. Registration, issuance, and processing fees are not priced here. Issuance stays off until the gates on this flow have been passed. Passing them in the sample does not authorize a real issuance.

How to read a transaction row

The Transactions screen lists sample rows. The hash, the block number, the cost, and the status are mock. The block figures are not a live height. Select a row for the recorded level, the finality, the policy decision, and the events.

The Domain, scope SGLD, is the domain currency.
A hub, such as SGLD-52, is a ledger tied to the domain.
An annex under a hub, such as SGLD-52-AX, sits on that ledger. It stays on the domain.
An annex with no hub in the scope, such as SGLD-0-AD, is the Direct Annex. It sits directly under the Domain.
Hops are the corridor count. Zero hops means inside the domain. One or more hops means a corridor.
Status Review means the row is held. Final in this table is a sample outcome, not a settlement on a live chain.

Who can do what

The signed-in sample user is pilot, role pilot customer admin. Invite by email adds an operator, a viewer, or an approver. The cockpit marks Users and roles complete only when an approver is on the list.

The permission table has three columns: Admin, Operator, and Viewer. Admin may edit zone drafts, resolve a REVIEW, request a policy publish, edit the tree, choose validator placements, submit a pilot test transaction, and approve a route. Operator may edit zone drafts, request a policy publish, edit the tree, and submit a pilot test transaction. Operator may not resolve a REVIEW, choose validator placements, or approve a route. Viewer is denied on every write in that table.

No customer role may start, stop, or rotate a validator. No customer role may see signing keys. No customer role may run treasury operations. Those stay with JIL. Removing a user or sending an invite changes the sample list in this browser. It does not create an enterprise account.

Activity and audit

Every change you make in this prototype is appended to the activity list: time, actor, module, action, the before and after, and the outcome. Filter by module. The sample already contains a few rows so the shape is visible.

That list lives with the configuration in this browser. In a production pilot the same record is an immutable server-side log. Reset demo clears the local sample back to the starting template, including this list. Export from the header downloads the configuration you have saved here. It is not an attestation.

What a later pilot keeps, and what it replaces

Keep the rules. The Domain is the sovereign domain currency. Hubs and annexes stay on that domain. Every Domain, Hub, and Annex uses the JIL L1 rail. Every transaction runs through ATCE. Corridor transactions require gas ignition. A global corridor also includes InterOp. Customer roles do not operate validators or hold signing keys.

Replace the sample. A later pilot brings its own domain name, its own hub and annex tree, its own zone text, its own connector registry, and its own users. The dollar figures, the block numbers, the outage switches, and the validator health marks do not carry over as facts. The capacity lease is not published. Filling in the fee ceiling on this screen does not publish it.

What this host will not do

It will not show a live jil-mainnet-2 height.
It will not issue a real token, sign a transaction, or move value.
It will not start a validator or reveal a key.
It will not price the capacity lease.
It will not start a node, read a height, or turn this proof into jil-mainnet-2. Test and deploy writes only the selected levels for this host. Desired, Observed, and Health stay labeled as sandbox until a real pilot is provisioned outside this template.

Test and deploy

The sidebar item Test and deploy runs an auditor, then can write the selected levels for this host. Choose the Domain alone, the Domain and a hub, or the whole domain, which is the Domain, hubs, and annexes. A hub or an annex always includes the Domain. An annex that sits on a hub also includes that hub. Test reads the tree and does not write a deployment. Deploy writes the selected levels only when every auditor item passes. The node is not started. No height is read. Publish to the public explorer stays a separate choice on the level dock and starts off.

Chain watcher

The sidebar item Public explorer opens the public page at /scan.html. That address works without a studio session, so anyone can open it outside the portal. It is the chain watcher for this demonstration and the equivalent of a block explorer. etherscan.io does not list this chain. The chain id is jil-poc-lari and the EVM chain id is 15601.

A level appears on that page only after you turn on Publish for that level on the level dock. Publish starts off. An inactive level stays visible as Inactive and refuses a ruling. The finalized height stays empty. This deploy does not start a node. Do not add this chain id to a wallet as if it were Ethereum mainnet. There is no public RPC, because the node is not started.

Look up a node code on /scan.html?q= and with GET /api/explorer/lookup?q= on this same host.

/scan.html

{{ scr.title }}

Route comparator