Accountable

Source-read ≠ self-reported. Accountable's Data Verification Network connects directly to each data source, retrieves financial data, and makes it cryptographically provable. Here's how it works ↓

5/ For more details on how our Data Verification Network works ↓ docs.accountable.capital/accountable-do…

Source-read ≠ self-reported. Accountable's Data Verification Network connects directly to each data source, retrieves financial data, and makes it cryptographically provable. Here's how it works ↓

We do not accept self-reported NAV. We compute it ourselves, checking balances and transactions from source, APIs when available, otherwise other documentation such as account statements received directly from banks, reconciliation files, or DocuSign attestations coming from the custodians. This can be correlated with NAV coming from providers such as NAV Consulting: docs.accountable.capital/accountable-do…

"The software connects directly to primary data sources, using API connections verified through secure enclaves and zkTLS attestations that create transport-layer proofs of data retrieval from source systems." so what primary data sources are accepted? One could stick a daily self-reported NAV report into an oracle and have that "not self reported"?

@mr8559 The software connects directly to each source: API connectors for offchain venues like exchanges and custodians, and direct onchain reads for blockchain data. We, as Accountable, did not retain access, but the software did. docs.accountable.capital/accountable-do…

@AccountableData oh you never obtained any API of their deribit account and just blindly reported what they told you to say

In recent days, we have received fair questions about the Main Street situation, what Accountable does, what we could and could not verify, and what we are changing as a result. We want to answer them plainly. When we started Accountable, our mission was to raise the transparency standard in this industry. Accountable is neutral verification infrastructure, not the LP, curator, or underwriter making the underlying risk decision. Our software connects to relevant venues and onchain sources through purpose-built connectors, producing cryptographically verifiable reports without taking custody of assets or requiring private keys. Reports can be shared privately with relevant counterparties or published publicly. The client’s reporting configuration determines what is publicly disclosed, as described in our documentation. When Main Street first came onboard, its public reporting showed an aggregate dollar value for the strategy’s backing, without a breakdown of the underlying assets. After onboarding, we did not retain an ongoing, source-level view of those reserves. As publicly observable onchain activity and related questions accumulated, we engaged directly with Main Street over an extended period and asked them to provide a current breakdown of reserves that would allow us to determine what was behind the reported number. Main Street did not provide it. The termination of the contract was not a rushed decision. It followed sustained efforts to obtain a verifiable breakdown of the reported reserves, after which Accountable terminated the agreement with immediate effect. Across our integrations, we have learned that transparency and legitimate strategy privacy require an active balance. Where public reporting is not sufficient for the risk being taken, those relying on it should push for either more public disclosure or a complete private view of the underlying reserves. In other integrations, that dialogue has led to more disclosure. In this case, it did not. As the role of the public reporting grew, the level of disclosure did not evolve with it. Over recent months, we have been working toward more granular requirements. For public-facing integrations, we will define clearer minimum disclosure and ongoing verification requirements, rather than rely on the market alone to determine where the boundary between privacy and transparency should sit. The tools exist. What is needed now is a collective demand for a higher standard of transparency.

Accountable has terminated its service agreement with MainStreet, effective immediately. MainStreet was unable to meet our verification standards. We recognize that markets relied on this feed and are working closely with partners across the ecosystem as the situation evolves. We will continue to hold this standard without exception.

@harunaalhasan19 @monad 💜

@AccountableData @monad Congrats Gmonad 💜

Accountable's YieldApp is the #1 destination on @monad. The largest vault infrastructure on Monad is one where every vault is continuously verifiable. gMonad.

@keoneHD @monad 🤝

@AccountableData @monad Congrats! 🧱🧱🧱

@YuzuMoneyX @monad @merkl_xyz 🍋

@AccountableData @monad @merkl_xyz 🍋

$MON rewards are now live across YieldApp. All active @monad vaults on Accountable's yield marketplace now carry fresh incentives, streamed directly to depositors' wallets through @merkl_xyz.

@Cattobreed @monad Verifiable Yield*

@AccountableData @monad Keep the Yield up on monad

@kamaromponx @monad gMonad.

@AccountableData @monad gMonad.

@aleeeexcool @monad 💪

@AccountableData @monad keep getting higher 💪

Explore all YieldApp vaults ↓ yield.accountable.capital