Commit a86b3df
committed
docs: two entries on the not-implemented list had stopped being true
That list is what anyone reads to answer "what is left", so a stale entry on
it is worse than a stale comment somewhere in the code - it sends the next
person to build something that already exists, or to trust a gap that closed.
The graduation router was listed as not implemented. It is built, and V-09
closed on Day 8 against the real HyperSwap position manager. What is actually
outstanding is narrower and worth stating precisely: its DEPLOYMENT, blocked on
first-party confirmation of three addresses that are immutable in its
constructor. Located and mutually verified on-chain is not the same claim as
the vendor saying so.
`/account` holdings were listed as needing a read that does not exist. They
ship, with portfolio value. P&L does not, and the reason is worth keeping: it
needs a cost basis, which means folding every trade rather than reading a
balance, and the history only exists from the indexer's start block. A P&L that
silently began mid-history would be wrong in the direction that flatters.1 parent 16ad0e0 commit a86b3df
1 file changed
Lines changed: 14 additions & 3 deletions
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
362 | 362 | | |
363 | 363 | | |
364 | 364 | | |
365 | | - | |
| 365 | + | |
| 366 | + | |
| 367 | + | |
| 368 | + | |
| 369 | + | |
| 370 | + | |
| 371 | + | |
| 372 | + | |
366 | 373 | | |
367 | 374 | | |
368 | 375 | | |
| |||
384 | 391 | | |
385 | 392 | | |
386 | 393 | | |
387 | | - | |
388 | | - | |
| 394 | + | |
| 395 | + | |
| 396 | + | |
| 397 | + | |
| 398 | + | |
| 399 | + | |
389 | 400 | | |
390 | 401 | | |
391 | 402 | | |
| |||
0 commit comments