Lotwise — Lot-by-lot ledger for on-chain yield income
LOTWISE
FILE 01 · LOT-BY-LOT LEDGER
What date was this lot received, at what price, and on which form line.
Lotwise reads your wallets in read-only mode, identifies every yield income event — lending interest, staking rewards, rebase value accrual, distributions from tokenised funds — then builds a lot-by-lot ledger priced at the moment of receipt. It exports a file that imports straight into tax filing software. Every ledger line links back to the originating transaction on the block explorer. No private keys, no signing permission.
Read-only access. Summary report preview is free. You pay when you need the export.
SHEET {{ sheetLabel }} · 12 LOTS SHOWNCLICK A LOTRECORDED
LOT
{{ selId }}
TYPE
{{ selType }}
PRICE AT RECEIPT
{{ selPrice }}
FORM LINE
{{ selLine }}
VIEW SOURCE{{ selTx }}
$12.40B
Segment market cap [1]
$1.16B
24h trading volume [2]
101
Active tokens [3]
76.13
Narrative momentum [4]
Core capabilities
LINE 02 / 05 BLOCKS
P0
BLOCK 01
The balance grows itself. The wallet history is empty.
Rebase tokens and value-accruing tokens produce income without producing a receive transaction. Tools that read transaction history see nothing, so they either miss the income entirely or record it at the wrong moment. Lotwise tracks balance movement and exchange-rate indices to reconstruct those events. Lending interest accruing into a debt-receipt token is test case number one for the classifier, not an edge case.
P0
BLOCK 02
Rebase, distribution and accrual are three different things.
The classifier assigns each on-chain event its accounting nature: lending interest, staking reward, rebase value increase, distribution from a tokenised fund, or not income at all. When it meets a contract with no rule, it marks the event unclassified and sends it to the queue — it does not guess. You assign the type yourself with an audit note, or wait for operations to write a new rule.
P0
BLOCK 03
Where this price came from, and at what time.
Every event is priced in fiat at the exact block timestamp, under a published valuation method applied consistently. The value used and the price source are stored in the record itself, not re-fetched later. Any line that used a derived price instead of a direct one is flagged as such.
P0
P2 · VERSION HISTORY
BLOCK 04
One click from a form line to a transaction hash.
Each income event opens a new lot whose cost basis is the recorded value. The lot's life is tracked through sales, swaps and withdrawals. Click a line and the exact transaction opens on the block explorer. The ledger is snapshotted at every export, with a change log for when classification rules are updated — so you can explain why this year's number differs from the one you filed last year.
P0
P1 · PARTNER API
BLOCK 05
A file that imports, plus a method that reads.
Export in the direct import format of mainstream tax filing software, plus a generic CSV and a summary report that states the valuation method in full. The classification ruleset is published as a verifiable code repository with a test suite per protocol. Accountants have to sign their name against the numbers — they trust a process they can read, not a black box. Wallets, retail brokerage apps and tax software vendors can embed it through the licensed API.
lotwise-2026-form.txtEXPORT DONE
lotwise-lots-2026.csvEXPORT DONE
summary-report.pdfMISSING DATA
GET /v1/lots?wallet=…VIEW SOURCE
How it works
LINE 03 / WALLET → LEDGER → FILE
01
Pick the period and jurisdiction
Every later step sits inside those two choices. Launch jurisdiction: undetermined.
02
Connect read-only wallets
Paste an address or connect read-only. Each wallet gets a label: yours, a dependent's, a client's.
03
The system builds the ledger
Scan per chain, classify, detect balance movement, price at the block timestamp with the source stored.
04
You clear the queue
Unclassified events are yours to assign with an audit note, or to file as a request for a new rule.
05
Export and close the file
Preview is free. Subscribe to unlock the export. The ledger is snapshotted at the moment of export.
Questions
LINE 04 / 05 ITEMS
No. Paste a wallet address, or connect a wallet in read-only mode. There is never a private key field and never a request for signing permission. In exchange, this is a dataset rich enough to identify a person and value their assets, so identifying data is encrypted at rest, every query is logged, and you can have your file deleted on request. An independent security audit is completed before the partner channel opens.
No. Lotwise exports data and forms. It gives no advice, recommends no tax election, and promises no saving. You file the export in your tax software, or hand it to your accountant. In the partner channel, closing the file sits with a licensed accountant.
That event is marked unclassified and held aside — it is not forced into a category. The list of officially supported protocols is published plainly; outside that list, the answer is "not supported yet". This is a real weakness of the product early on: rule coverage accumulates over time and cannot be bought quickly. Every new protocol, token standard and tokenised-fund issuer is another ruleset to write and maintain.
You import the exchange's transaction export, the system reconciles it against the on-chain ledger and flags anything at risk of overlap when assets move between exchange and wallet; you confirm which record to keep. This capability is P1 — the product works end to end for purely on-chain users first.
The asset surface already exists and does not depend on whether the market is being talked about: segment market cap $12.40B, 24h volume $1.16B, 101 active tokens, momentum 76.13. Attention is very thin — the narrative was mentioned 4 times in the measurement window, mentions changed -12.0% in 24h, spread 48%, measured demand 8.40. The income events that need recording are already real, and rebuilding a lot ledger for a tax year that has already passed cannot be done backwards through time.
