Heartank®Developersអ្នកអភិវឌ្ឍន៍Log inចូល

The sandboxកន្លែងសាកល្បង

Try Thank with HeartBank® end to end before anything counts: your app's own code, test persons, and test passkeys your code or an agent can press. Nothing in it is real.សាកល្បង Thank with HeartBank® ពីដើមដល់ចប់ មុនពេលអ្វីៗរាប់៖ កូដរបស់កម្មវិធីអ្នកផ្ទាល់ មនុស្សសាកល្បង និងសោសាកល្បងដែលកូដ ឬភ្នាក់ងាររបស់អ្នកអាចចុចបាន។ គ្មានអ្វីនៅក្នុងវាពិតប្រាកដទេ។

1 Ask for Log in១ ស្នើ Log in
On your app's page on the dashboard. The sandbox knows an app by its Log-in client id; approval isn't needed there.នៅលើទំព័រកម្មវិធីរបស់អ្នកនៅលើផ្ទាំងគ្រប់គ្រង។ កន្លែងសាកល្បងស្គាល់កម្មវិធីតាមលេខសម្គាល់អតិថិជន Log in របស់វា។ មិនចាំបាច់មានការអនុម័តនៅទីនោះទេ។
2 Make test persons២ បង្កើតមនុស្សសាកល្បង
On the app's Sandbox card, or POST https://sandbox.333.eco/persons. Each comes with the sub and pidToken Log in would give you.នៅលើកាតកន្លែងសាកល្បងរបស់កម្មវិធី ឬ POST https://sandbox.333.eco/persons។ ម្នាក់ៗមកជាមួយ sub និង pidToken ដែល Log in នឹងផ្តល់ឱ្យអ្នក។
3 Run your Thank code៣ ដំណើរការកូដ Thank របស់អ្នក
Against https://sandbox.333.eco/ledger in place of https://ledger.333.eco: the same calls, the same answers.ធៀបនឹង https://sandbox.333.eco/ledger ជំនួស https://ledger.333.eco៖ ការហៅដូចគ្នា ចម្លើយដូចគ្នា។
4 Press as a test person៤ ចុចជាមនុស្សសាកល្បង
Send a browser to https://sandbox.333.eco/press as you would to sign.333.eco, or press from code with POST /press/api, or let an agent call sandbox_press.បញ្ជូនកម្មវិធីរុករកទៅ https://sandbox.333.eco/press ដូចដែលអ្នកធ្វើទៅ sign.333.eco ឬចុចពីកូដដោយ POST /press/api ឬឱ្យភ្នាក់ងារហៅ sandbox_press។
// The /thank sample, with only the address changed, and a test person in place of a log-in.
const SANDBOX = "https://sandbox.333.eco";
// Your client assertion: iss = sub = your app's Log-in client id (hbc_…). aud = the exact address called for the sandbox's own steps,
// and the ledger's base address (https://sandbox.333.eco/ledger) for every ledger call, as https://ledger.333.eco in production.
const call = async (path, body, aud = SANDBOX + path) => (await fetch(SANDBOX + path, { method: "POST",
  headers: { "content-type": "application/json", "x-client-assertion": await clientAssertion(aud) }, body: JSON.stringify(body) })).json();

const { person: giver } = await call("/persons", { label: "Alice" });
const { person: receiver } = await call("/persons", { label: "Bob" });
// 1. Prepare (aud = https://sandbox.333.eco/ledger, as https://ledger.333.eco in production).
const { pending, ticket } = await call("/ledger/v1/prepare", { ref, ledger: "kiitos",
  pidToken: giver.pidToken, sub: giver.sub, to: { pidToken: receiver.pidToken, sub: receiver.sub } }, SANDBOX + "/ledger");
// 2. The press: a test passkey's, the one step that differs. (In production: the person, at sign.333.eco.)
const { result } = await call("/press/api", { ticket, person: giver.id });
const { pressToken } = await (await fetch(SANDBOX + "/press/wrap", { method: "POST", body: new URLSearchParams({ result }) })).json();
// 3. Commit.
const answer = await call("/ledger/v1/commit", { ref, pending, pressToken }, SANDBOX + "/ledger");

Everything that differs from productionអ្វីៗទាំងអស់ដែលខុសពីផលិតកម្ម

The address. Test persons in place of people. An agent may press here, for a test person only, and a press made here verifies nowhere else. A season a week: every Monday 00:00–00:15 UTC nothing is written while last week's log gets its last checkpoint, then the thanks and the places are wiped and a new log begins; test persons stay. Each week's log is at https://sandbox.333.eco/log/<its Monday>/, closed daily at 00:05 UTC and kept 7 days after the week. No zero-sum proof and no outside timestamps for this throwaway log. Free, with no review: at most 20 test persons and 1,000 prepares per app per UTC day.អាសយដ្ឋាន។ មនុស្សសាកល្បងជំនួសមនុស្សពិត។ ភ្នាក់ងារអាចចុចនៅទីនេះ សម្រាប់តែមនុស្សសាកល្បងប៉ុណ្ណោះ ហើយការចុចនៅទីនេះមិនអាចផ្ទៀងផ្ទាត់នៅកន្លែងផ្សេងទេ។ មួយរដូវក្នុងមួយសប្តាហ៍៖ រៀងរាល់ថ្ងៃច័ន្ទ ម៉ោង ០០:០០–០០:១៥ UTC គ្មានអ្វីត្រូវបានសរសេរទេ ខណៈកំណត់ហេតុនៃសប្តាហ៍មុនទទួលបានចំណុចត្រួតពិនិត្យចុងក្រោយ បន្ទាប់មកការអរគុណ និងទីកន្លែងត្រូវបានលុប ហើយកំណត់ហេតុថ្មីចាប់ផ្តើម។ មនុស្សសាកល្បងនៅដដែល។ កំណត់ហេតុនៃសប្តាហ៍នីមួយៗនៅ https://sandbox.333.eco/log/<ថ្ងៃច័ន្ទរបស់វា>/ បិទរៀងរាល់ថ្ងៃ នៅម៉ោង ០០:០៥ UTC ហើយរក្សាទុក ៧ ថ្ងៃបន្ទាប់ពីសប្តាហ៍។ គ្មានភស្តុតាងផលបូកសូន្យ និងគ្មានត្រាពេលវេលាពីខាងក្រៅសម្រាប់កំណត់ហេតុបោះចោលនេះទេ។ ឥតគិតថ្លៃ គ្មានការពិនិត្យ៖ យ៉ាងច្រើន ២០ មនុស្សសាកល្បង និង ១,០០០ ការរៀបចំក្នុងមួយកម្មវិធីក្នុងមួយថ្ងៃ UTC។

The same rule, and refusals just as silentច្បាប់ដូចគ្នា ហើយការបដិសេធក៏ស្ងាត់ដូចគ្នា

The sandbox ledger is the permanent ledger's own code, running the newest published rule. A thank it declines answers {"written": false} and nothing more, exactly as in production, so your app is built for the answers it will really get.បញ្ជីកន្លែងសាកល្បងគឺជាកូដផ្ទាល់របស់បញ្ជីអចិន្ត្រៃយ៍ ដែលដំណើរការច្បាប់ដែលបានបោះពុម្ពថ្មីបំផុត។ ការអរគុណដែលវាបដិសេធ ឆ្លើយ {"written": false} ហើយគ្មានអ្វីទៀតទេ ដូចក្នុងផលិតកម្មដែរ ដូច្នេះកម្មវិធីរបស់អ្នកត្រូវបានបង្កើតសម្រាប់ចម្លើយដែលវានឹងទទួលបានពិតប្រាកដ។

An agent can do everything except the pressភ្នាក់ងារអាចធ្វើអ្វីៗគ្រប់យ៉ាង លើកលែងតែការចុច

That stays true where it counts: in the sandbox an agent may press, because a test person is nobody and a test press verifies nowhere else. In production every press is a person's own passkey.នោះនៅតែពិតនៅកន្លែងដែលវាសំខាន់៖ នៅក្នុងកន្លែងសាកល្បង ភ្នាក់ងារអាចចុចបាន ព្រោះមនុស្សសាកល្បងមិនមែនជានរណាម្នាក់ទេ ហើយការចុចសាកល្បងមិនអាចផ្ទៀងផ្ទាត់នៅកន្លែងផ្សេងទេ។ ក្នុងផលិតកម្ម ការចុចនីមួយៗគឺជា passkey ផ្ទាល់ខ្លួនរបស់មនុស្សម្នាក់។

ឯកសារយោងខាងក្រោមមានជាភាសាអង់គ្លេសតែប៉ុណ្ណោះ។

The sandbox: reference

Try Thank with HeartBank® end to end before anything counts: test persons, and test passkeys your code or an agent can press. Nothing in it is real. Thank's own calls run here at https://sandbox.333.eco/ledger (/v1/prepare, /v1/commit, /v1/place, /v1/aura; your assertion's aud is that base address, as https://ledger.333.eco in production), and the press page at https://sandbox.333.eco/press.

The developers' sandbox (developers.333.eco SPEC §8.1), read from its live code: repo 333eco/developers.333.eco, sandbox/src/server.ts. The sandbox ledger at https://sandbox.333.eco/ledger is the ledger's own code: its API is Thank with HeartBank®'s, at that address. These are the sandbox's own steps: test persons in place of a person's log-in, and the twins of login.333.eco's /press/hint and /press/wrap (same request, same answer); /press/api is the one step that exists only here.

⛔ Nothing in it is real. A test person is nobody; a press made here is a test passkey's, for sandbox.333.eco, and verifies nowhere else; every Monday 00:00–00:15 UTC nothing is written while the week rolls: last week's log gets its last checkpoint, then the thanks and the places are wiped and a new log begins (test persons stay). An app is in the sandbox once it has asked for Log in on the dashboard (approval isn't needed here). At most 20 test persons and 1,000 prepares per app per UTC day.

The week's log: each week has its own log, named sandbox.333.eco/log/<its Monday, YYYY-MM-DD>, and a receipt names the week it was written in. Its files are at https://sandbox.333.eco/log/<Monday>/: checkpoint (a signed note, the one file that changes), checkpoints/<size>, tile/… (C2SP tlog-tiles), vkey (the week's verifier key, Ed25519, named for that week, so a checkpoint verifies under one week only) and, once the week has ended, final (its last size). The log closes once a day at 00:05 UTC, so a thank appears in the next day's checkpoint; the week's files stay 7 days after it ends. Like production, your app gets only a receipt's id: the whole receipt goes to its person's own record, which the sandbox does not have, so here you check the tree (the checkpoint against the vkey, the root from the tiles), not your own receipt.

Your assertion, everywhere here: a fresh ES256 JWT, iss = sub = your app's Log-in client id (hbc_…; get_app and the dashboard show it), one-use jti, at most 5 minutes old. aud is the exact address called for the sandbox's own steps (/persons, /persons/{id}, /press/hint, /press/api), and the ledger's base address, https://sandbox.333.eco/ledger, for every ledger call. A kid in the header is optional: with one key at your key URL it is found without it; send it when you publish several. /press/wrap takes no assertion: it knows the app from the result itself.

GET https://sandbox.333.eco/persons

Your app's test persons

Every test person of the calling app, oldest first, each with a fresh pidToken (as each log-in gives one).

Who may call it: Your app's server proves itself as it does at the ledger: a fresh ES256 JWT, iss = sub = your app's Log-in client id (hbc_…), aud = the exact address called, at most 5 minutes old, a jti never used before. Your keys are read from the key URL on your app's Log in. ⛔ Never sent from a browser or a phone.

Answers

  • 200 The test persons. { persons }
  • 401 Not an app the sandbox knows, or a bad assertion. { error }

What a success answer holds

FieldTypeWhat it is
personsobject[]

On the MCP server: not a tool: your app's server, with its own key; an agent uses the developer tool sandbox_add_person, behind sign-on

POST https://sandbox.333.eco/persons

Make a test person

At most 20 per app. They stay through the weekly wipe, until removed or the app is deleted.

Who may call it: Your app's server proves itself as it does at the ledger: a fresh ES256 JWT, iss = sub = your app's Log-in client id (hbc_…), aud = the exact address called, at most 5 minutes old, a jti never used before. Your keys are read from the key URL on your app's Log in. ⛔ Never sent from a browser or a phone.

Body application/json

FieldTypeWhat it is
labelstringYour own name for them, such as Alice.

Answers

  • 200 The new test person. { person }
  • 400 A bad label. { error }
  • 401 Not an app the sandbox knows, or a bad assertion. { error }
  • 409 Already 20. { error }

What a success answer holds

FieldTypeWhat it is
person{ id, label, sub, pidToken }
person.idstringThe test person's id here; the one /press/api and the page press as.
person.labelstringYour own name for them (1 to 40 characters).
person.substringYour app's id for them, as Log in gives one.
person.pidTokenstringAs Log in's pid_token claim: signed by the sandbox and sealed to the sandbox ledger. A fresh one each time; good for 180 days; the sandbox's alone.

On the MCP server: not a tool: a write; an agent uses the developer tool sandbox_add_person, behind sign-on

DELETE https://sandbox.333.eco/persons/{id}

Remove a test person

Who may call it: Your app's server proves itself as it does at the ledger: a fresh ES256 JWT, iss = sub = your app's Log-in client id (hbc_…), aud = the exact address called, at most 5 minutes old, a jti never used before. Your keys are read from the key URL on your app's Log in. ⛔ Never sent from a browser or a phone.

Parameters

NameTypeWhat it is
id (path)string

Answers

  • 200 Removed. { deleted }
  • 401 Not an app the sandbox knows, or a bad assertion. { error }
  • 404 No test person of your app has that id. { error }

What a success answer holds

FieldTypeWhat it is
deletedtrue

On the MCP server: not a tool: a write, on your app's own key

POST https://sandbox.333.eco/press/hint

Which test person is the giver (twin of login.333.eco/press/hint)

The same request and answer as production's: the hint narrows the press page to the giver. A narrowing, never a gate.

Who may call it: Sent as FORM fields, not a header, as at login.333.eco: client_assertion_type = urn:ietf:params:oauth:client-assertion-type:jwt-bearer and client_assertion = the same ES256 JWT, aud = this endpoint's address.

Body application/x-www-form-urlencoded

FieldTypeWhat it is
client_assertion_type"urn:ietf:params:oauth:client-assertion-type:jwt-bearer"
client_assertionstring
substringYour app's id for the giver.

Answers

  • 200 A hint for the press page's hint fragment field. { hint }
  • 401 A bad assertion. { error }
  • 403 Not an app the sandbox knows. { error }
  • 404 No test person of your app has that sub. { error }

What a success answer holds

FieldTypeWhat it is
hintstring

On the MCP server: not a tool: your app's server, with its own key

POST https://sandbox.333.eco/press/api

A test press, for code and agents (the sandbox only)

Presses a test person's test passkey for a ticket the sandbox ledger's prepare returned, and returns the same result the press page brings back to your return page. ⛔ Only here: in production every press is a person's own passkey. ⛔ Only a ticket the sandbox ledger signed, and only your own app's.

Who may call it: Your app's server proves itself as it does at the ledger: a fresh ES256 JWT, iss = sub = your app's Log-in client id (hbc_…), aud = the exact address called, at most 5 minutes old, a jti never used before. Your keys are read from the key URL on your app's Log in. ⛔ Never sent from a browser or a phone.

Body application/json

FieldTypeWhat it is
ticketstring
personstringThe test person who presses: for a Kiitos, the giver.

Answers

  • 200 The result, good once and for 2 minutes, at /press/wrap. { result }
  • 400 Not a ticket the sandbox ledger made, or it expired (unknown_flow). { error }
  • 401 Not an app the sandbox knows, or a bad assertion. { error }
  • 403 Another app's ticket. { error }
  • 404 No test person of your app has that id. { error }

What a success answer holds

FieldTypeWhat it is
resultstring

On the MCP server: not a tool: your app's own key; an agent uses the developer tool sandbox_press, behind sign-on

POST https://sandbox.333.eco/press/wrap

Exchange a result for a pressToken (twin of login.333.eco/press/wrap)

The same request and answer as production's: the press result from the press page (or /press/api), exchanged by your server for the pressToken POST /ledger/v1/commit takes.

Who may call it: anyone, no key

Body application/x-www-form-urlencoded

FieldTypeWhat it is
resultstring

Answers

  • 200 The pressToken for POST /ledger/v1/commit. { pressToken }
  • 400 The result was refused, or already used (replayed). { error }
  • 403 The result names an app the sandbox doesn't know (it reads the app from the result, which only the sandbox could have signed). { error }

What a success answer holds

FieldTypeWhat it is
pressTokenstring

On the MCP server: not a tool: your app's server, after the test press