You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit bb362a3
Browse filesBrowse the repository at this point in the historyBrowse files
feat(meta-legion): move /meta-legion to Legion Exchange v2 (#1095)
* feat(meta-legion): move /meta-legion to Legion Exchange v2
v2 (SP3EF02CC2CGWJ327TXXW7JD4B9K9F1R0FSVY3659.legion-exchange-v2) replaces
v1's human resolvers. Every legion now asks one fixed question: will any of
these Bitcoin addresses bond in pox-5 after the legion was created and by
its deadline? YES settles by an on-chain Bitcoin proof (resolve-bonded),
accepted until 1,008 blocks after the deadline; NO by resolve-idle after
that.
- Fold the v2 prints: create-legion carries label, scripts, deadline and
created-at; resolve-bonded and resolve-idle replace resolve and
void-legion
- Phases follow the contract: trading, proof window, awaiting
resolve-idle, settled
- Show every legion's addresses, decoded from the stored output scripts
(P2PK outputs such as Satoshi's genesis key are named, since they have
no standard address), and both countdowns: deadline and proof window
- Legion 0's label and created-at are v2's deploy values
- The exchange chainhook targets v2 as aibtc-legion-exchange-v2-mainnet
* refactor(meta-legion): trim the page copy
Drop the explanatory paragraphs (hero, scoreboard, market, footer and the
per-legion sub-line) down to one short line where one is needed, and fix
the closing call to action, which still described v1's resolvers.
Copy file name to clipboardExpand all lines: app/api/meta-legion/route.ts
+3-3Lines changed: 3 additions & 3 deletions
Original file line number
Diff line number
Diff line change
@@ -19,19 +19,19 @@ export async function GET(request: NextRequest) {
19
19
endpoint: "/api/meta-legion",
20
20
method: "GET",
21
21
description:
22
-
"State of the Legion Exchange: every legion is a yes/no question with its own YES/NO share market paid in sBTC. Legion 0, the meta legion, asks whether at least `target` legions clear the trading bar in each of the three counted epochs before the close. The contract settles it from its own scoreboard. Folded from the exchange's print events, delivered by a Hiro chainhook; read-only.",
22
+
"State of the Legion Exchange v2: every legion asks whether any of a set of Bitcoin addresses bonds in pox-5 before a deadline, with its own YES/NO share market paid in sBTC. YES settles by an on-chain Bitcoin proof (resolve-bonded), NO by resolve-idle after the proof grace. Legion 0, the meta legion, asks whether at least `target` legions clear the trading bar in each of the three counted epochs before the close. The contract settles it from its own scoreboard. Folded from the exchange's print events, delivered by a Hiro chainhook; read-only.",
"{ id, label, creator, scripts (Bitcoin output scripts, 0x hex; the question is whether any bonds in pox-5 after createdAt and by deadline), deadline, createdAt, status (0 open, 1 YES bonded, 2 NO idle), collateral, supply, stats[{ epoch, volume, traders, qualified }] }",
35
35
orders:
36
36
"Orders with shares left, across every legion: { id, kind (offer | bid), legion, side (1 YES, 0 NO), maker, price (ten-thousandths of a sat per share), remaining }",
37
37
feed: "The 60 most recent exchange events, newest first: { txid, event, blockHeight, data }",
0 commit comments