Bedrock: financial control for digital asset treasury teams using written options

Written options can look clean at the strategy level. A company holds digital assets. It writes covered calls against part of its position. It may write cash-secured puts as part of a broader treasury strategy. Premium is received. Positions expire, are bought back, or are assigned.

The accounting and tax reality is not that clean. Finance still has to prove how yield activity connects to the underlying lots, restrictions, tax treatment, accounting outputs, and audit evidence.

Every option position creates a chain of questions that the finance team has to answer later. Which lots were tied to the position? Were those lots still available for sale or transfer? Did settlement affect a specific lot? Did the option lifecycle affect holding-period analysis? Does premium treatment reconcile with the underlying asset movement? Can the close package explain the full path without rebuilding the story from exports and spreadsheets?

That is where ordinary crypto reporting workflows start to break down. Portfolio dashboards can show balances. Tax tools can produce year-end outputs. Spreadsheets can document a point-in-time assumption. But treasury teams generating yield through options need something more controlled: a record that keeps the option, the lot, the restriction, the settlement event, the accounting view, and the audit trail connected.

Bedrock is built for that operating reality.

Bedrock sits between raw digital asset activity and the financial outputs an institution needs to rely on.

When treasury activity enters Bedrock, it becomes part of a profile-scoped financial record. Wallet movements, venue activity, option schedules, mining records, treasury sales, and structured imports are organized into ledgers, transactions, lots, rules, and reporting views. The important point is not just that the data is collected. It is that the data remains connected to the financial decisions that affect reported numbers.

A written covered call, for example, is not treated as an isolated schedule item. It is connected to the treasury inventory behind it. Bedrock can show the lots tied to the position, the encumbrance against those lots, the option premium and lifecycle status, the settlement or close event, and the audit history around the decision. The same principle applies to cash-secured puts, where the option position needs to be understood in the context of treasury policy, settlement exposure, and reporting treatment.

That continuity is what gives CFOs and controllers a more defensible record. The final report is only useful if the team can explain how the number was produced, which decisions shaped it, and where the evidence lives.

For digital asset treasury companies, a balance by asset is not enough. The financial record needs to preserve which lots are held, where they came from, what basis they carry, how long they have been held, whether they are available, and whether they have been selected, transferred, sold, assigned, locked, or encumbered.

Bedrock tracks inventory at the lot level, including quantity, basis, acquisition date, holding period, source context, remaining amount, allocation history, and availability. That lot-level view becomes the foundation for tax-lot selection, written option workflows, internal transfers, period-end reporting, and audit review.

This is especially important when assets move across wallets, custodians, venues, cold storage, and operating accounts. A same-taxpayer transfer should not erase the tax and audit history behind the asset. Bedrock is designed to preserve lot identity, basis, and acquisition-date continuity across internal movements so the organization does not lose the story behind the position.

A treasury team writing covered calls or cash-secured puts needs more than a list of open contracts. It needs to know how each position interacts with the underlying financial record.

Bedrock supports written option workflows by connecting option entry, premium treatment, lifecycle status, lot assignment, option-linked encumbrances, settlement reconciliation, and position history. That means a finance team can understand not only that an option existed, but how it affected inventory, availability, reporting, and review.

The practical value shows up when something changes. If a position expires, is exercised, or is bought back, the event needs to flow through the record. If physical settlement occurs, the option close event needs to reconcile to the spot delivery transaction. If a lot was tied to the position, that restriction needs to be visible before treasury makes another decision with the same inventory.

That is the difference between tracking options and controlling the financial consequences of options.

Period-end reporting becomes fragile when tax, accounting, treasury, and audit stakeholders each maintain their own version of the facts. One file has exchange activity. Another has wallet history. Another has the option schedule. Another has tax-lot assumptions. Another has the close workbook. Another has auditor responses.

Bedrock reduces that fragmentation by producing reporting views from the same record that tracks lots, option activity, encumbrances, decisions, and audit events. It supports finance workflows around ASU 2023-08 fair-value reporting, period-end remeasurement, crypto roll-forward reporting, P&L impact views, mining revenue detail, and close-period review.

The result is a cleaner operating model for CFOs and controllers. Treasury can see what is actually available. Tax advisors can review lot-level decisions. Accounting can work from period-end reporting views. Auditors can trace outputs back to source activity, approvals, overrides, settlement events, and close context.

When each stakeholder can work from the same record, the organization has fewer reconciliation gaps and a stronger basis for review.

Bedrock gives digital asset treasury finance teams a controlled way to manage the messy intersection of digital asset inventory, written options, tax-lot accounting, and reporting obligations. It supports digital asset subledger workflows, written covered calls, written cash-secured puts, option premium and lifecycle tracking, option-linked lot encumbrances, settlement reconciliation, specific identification support, basis and acquisition-date continuity, internal wallet and venue transfers, ASU 2023-08 reporting support, period close exceptions, profile-scoped controls, and audit evidence.

The goal is not to create another place to view crypto activity. The goal is to make the financial record explainable.

When a board member, tax advisor, auditor, or internal stakeholder asks how a number was produced, the answer should not require rebuilding the story across exports, workpapers, and spreadsheets. With Bedrock, treasury activity, written options, lot-level decisions, reporting outputs, and audit evidence can trace back to the same financial record.