A carbon promise with a public certificate.
A real carbon credit is retired for the request. RouteLock records the promise, checks the request, and links the provider's certificate to the completed service.
RouteLock Agent checks whether a real-world service request is eligible, records the decision, and refuses when the evidence is not strong enough. It never controls customer funds: payment moves only after the provider's work is proved.
The real-world asset is the provider's collateral-backed promise to perform. RouteLock Agent checks that promise before payment and records proof after work. Choose the service lane you want to inspect.
A real carbon credit is retired for the request. RouteLock records the promise, checks the request, and links the provider's certificate to the completed service.
The service is being tested with a real provider. RouteLock will not take a compute request until the work, the result and the provider's proof can all be checked.
The live carbon service is available when a backed offer is ready. RouteLock checks the request first, then your wallet approves each payment step. If the service cannot be safely verified, it stops.
Choose a backed service offer and a live carbon credit. RouteLock reviews the request before your wallet approves anything, then links the public certificate to the finished service.
Connect the issuer wallet that owns the service. The API reads the live offer; only your wallet can create an offer or move its collateral.
Connect the provider wallet to read its offers.
RouteLock is finishing the real provider run for this service. The request will open only when the work, result and provider proof can all be checked from start to finish.
The compute adapter, policy check and BOT Chain testnet contracts are built. The customer request waits for one real provider lease and a public result so the page never presents a fake completion.
This is the provider side of the BOT Chain lane. The provider run must create a real compute lease, check its result and commit the evidence before customer payment opens.
Built and preflighted; the live lease and ingress proof are still the activation gate.
The generic entitlement, escrow and registry contracts are deployed on testnet 968.
Offer creation and collateral are wallet-controlled. The provider proof is never invented by this page.
Once the real provider workload returns a checkable result, this page can expose the same customer flow as X Layer: request, review, work, proof and settlement.
A provider sets the offer and puts money behind the promise. A customer chooses the service. RouteLock checks the request, then records what was actually delivered before the provider is paid.
The provider publishes the price, terms and available supply, then deposits enough USD₮0 into RouteLock to cover every promise.
The customer connects a wallet, chooses a live credit and submits their name and retirement message. No payment moves before the request is checked.
The request is reviewed against the live carbon inventory. If approved, the provider retires the credit and receives a public certificate.
The certificate and payment result are written into the service record. The provider is paid only after that proof is present; otherwise the customer is protected.
The provider publishes the workload, acceptable use rules, price and available capacity on the BOT Chain compute lane.
The customer chooses the service and sends a request. RouteLock checks the request before a provider is hired or customer money is released.
RouteLock creates a real compute lease, waits for the named service to come online and checks the returned endpoint.
The lease, result and provider response become the proof of work. The customer flow will open when that complete run is ready for live use.
One service is live now. The other is being completed carefully, with no demo work presented as proof.
Carbon credits have been retired and the provider certificates can be opened and checked.
See the carbon serviceThe compute service is built and being tested with a real provider. It will open only when the complete proof is ready.
See compute statusChecking current service status…
Connect your wallet when you are ready to approve a live service. RouteLock never receives your private key. Your wallet will show every payment and approval before it happens.