Roman M

Founder at Treasury Desk | Writing Before the Journal Entry — stablecoin & on-chain treasury notes for CFO/accounting advisers

[Roman M @treasdesk]

We’re building Treasury Desk from Hong Kong — global by design.

I’m writing Before the Journal Entry to share what we’re learning about stablecoin and on-chain treasury workflows.

The question behind the work:

What should finance teams understand before stablecoin or on-chain activity becomes a journal entry, board memo, client explanation, treasury review, or governance discussion?

We’re especially interested in the messy middle:

- source trails
- missing evidence
- stablecoin exposure
- issuer and depeg context
- wallet / account evidence
- accounting record vs treasury-risk signal
- board and reviewer questions
- human-reviewed AI workflows

Treasury Desk is read-only.

We do not custody funds.
We do not execute transactions.
We do not provide investment, legal, tax, accounting, or compliance advice.

The goal is to make crypto-adjacent treasury context more reviewable for humans.

If you are a CFO, controller, adviser, accountant, treasury operator, DAO finance lead, or web3 finance builder working near these questions, I’d love your critique.

[Roman M @treasdesk]

Dashboards help. I use them all the time.

But I wouldn’t hand a reviewer just a screenshot.

For month-end, I’d want the source, timestamp, address/account, assumptions, gaps, and a note on what the balance does not prove.

[Roman M @treasdesk]

I like this because it separates the exciting part from the finance work. A payment can be automated. But at month-end someone still has to explain: who initiated it, what signed, which policy allowed it, what failed or retried, and what evidence survived the close.

[Treasury Desk @treasurydesk]

1/ A payment method is not a close file.

Some documented machine-payment flows can automate parts of the transaction path.

They do not automatically create month-end evidence.

[Roman M @treasdesk]

@SnapshotLabs @ensdomains @safe For this type of proposal, I’d start with scope before opinion: what authority is being renewed, what history triggered it, what limits exist, and what remains unknown?

[Roman M @treasdesk]

24/7 transferability is not the same as 24/7 liquidity. If tokenized assets enter treasury discussions, the first useful artifact is a simple matrix: transfer, secondary liquidity, minting, redemption, constraints.

[Ondo Finance @OndoFinance]

Real 24/7 trading for tokenized stocks is here.

In a landmark first for the industry, the most popular Ondo tokenized stocks and ETFs can now be minted & redeemed anytime.

While others have claimed 24/7 trading, this has only ever been for CEX or DEX transfers, with actual minting and redemption limited to traditional market hours. Now, tokenized stocks are truly trading 24/7:

✅ Overnight
✅ Weekends
✅ Public holidays

The first wave of 24/7 assets are SPYon, QQQon, CRCLon, NVDAon, TSLAon, and GOOGLon, with more to follow.

This builds on existing 24/7 permissionless transfers of Ondo tokenized stocks, moving the industry another step closer to the always-on onchain markets that will define the future of global finance.

Live now on Ethereum & BNB Chain, with Solana coming soon.

[Roman M @treasdesk]

@OndoFinance The transfer vs mint/redeem distinction matters a lot here. For treasury conversations, I’d want that separated clearly before treating “24/7” as a liquidity claim.

[Roman M @treasdesk]

@bra1nycyber Hi, sure. Connected

[Roman M @treasdesk]

Looking to #connect with founders and operators building around AI, finance ops, stablecoins, treasury, reporting, on-chain workflows, frontend, backend, full stack, devops, leetcode, AI/ML, data science, freelancing, startup, tech, or UI-UX.

I’m building Treasury Desk and trying to learn from people close to the real workflow.

Introduce yourself below — what are you building?

[Roman M @treasdesk]

Compliance features are not the same thing as review evidence. The finance team still needs the boring after-the-fact pack: what policy applied, what happened, what exceptions appeared, and who reviewed it.

[Arbitrum @arbitrum]

Businesses want the speed and efficiency of blockchain without sacrificing compliance.

The Arbitrum Platform enables businesses to define and enforce compliance policies at the infrastructure layer with screening, monitoring, access controls, and reporting built in.

[Roman M @treasdesk]

@arbitrum The infra layer matters. But finance teams will still ask the second set of questions: which policy applied, what exceptions showed up, and who reviewed them afterward?

[Roman M @treasdesk]

Live dashboards are useful. But month-end work usually needs something more boring: a balance tied to a date, a source, and a reviewer. Point-in-time balances help with that.

[Dune @Dune]

Tracking exchange float, custodian balances, or lending market exposure across chains is harder than it should be — compliance teams know this better than anyone.

Dune's new EVM Balances collection covers any group of addresses across 21 EVM chains. Filter by token, filter by date range. Always the exact balance in effect for the period you're investigating, not stale daily snapshots.

Explore the new EVM Balances collection → https://t.co/tDjHOGoJf4

[Roman M @treasdesk]

@Dune Underrated primitive. For finance teams, the question is often not “what is the balance now?” It is “what was true on the review date?”

[Roman M @treasdesk]

Governance risk is often easier to discuss after the scope is mapped. Before “for or against,” I’d want:
authority, limits, history, implementation details, open questions.

[Snapshot.eth @SnapshotLabs]

@ensdomains is voting on a to renew its Security Council for two more years before its veto authority expires July 24th.

The council was created after a 2024 governance vulnerability could have enabled a ~$150M treasury theft. Its role stays narrow: 4 of 8 @safe signers can only cancel malicious proposals, not create or amend governance actions.

The renewal also uses an audited @blockful_io contract with zero findings from @NethermindSec that makes future extensions defineable by a single governance vote rather than a fresh deployment and role re-grant. One inactive seat rotates to @Coltron_eth.

Support is broad, but the scope debate matters. @nicksdjohnson supports the backstop, but says it must not veto legitimate proposals just because signers disagree with them. He voted abstain. @bcvfinance argues the two-year authority window is too long for delegates to meaningfully challenge.

35 wallets have cast 4,052,110 $ENS so far: 19.4% For, 0% Against, 80.6% Abstain.

Voting closes June 28th at 4:43pm UTC.

Proposal: https://t.co/PxXEhE8fjx

[Roman M @treasdesk]

@sparkdotfi @Uniswap Shared liquidity is a big step. But the controller/adviser question is still pretty practical: which pool, which route, what changed, and what can we actually show later?

[Roman M @treasdesk]

Stablecoin rails are becoming more FX-like. The next hard part is less exciting but important: the paper trail finance teams can review after the route happened.

[Spark @sparkdotfi]

Introducing the Stablecoin FX Layer.

Every bank, fintech and payment provider is launching stablecoins. But every new stablecoin fragments liquidity.

Today, Spark introduces the Stablecoin FX Layer, built on @Uniswap v4, a shared liquidity infrastructure that allows stablecoins to access shared liquidity instead of building isolated pools.

The initial deployment brings approximately $150M of liquidity to Uniswap v4 across the first USDS/PYUSD and USDS/USDT pools.

This is just the beginning.

Learn more:
https://t.co/S5xVANjUt4

[Roman M @treasdesk]

@Gaurav_dev01 @treasurydesk Great question. Spreadsheets track data. Accounting tools record transactions. The hard part we’re focused on is the layer in between: source trails, missing context, exceptions, and reviewer-ready notes before the journal entry.

[Roman M @treasdesk]

@martinhrtech @X Hi! Let’s connect. I’m building @treasurydesk for teams that need clearer reporting around wallets, stablecoins, and on-chain treasury activity.

[Roman M @treasdesk]

@Avinaba_ @X @grok Hi! Happy to connect. I’m building @treasurydesk — focused on read-only treasury monitoring, evidence trails, and reviewer-ready context.

[Roman M @treasdesk]

@DangwalAlok Hi! Let’s connect. I’m building @treasurydesk to help teams separate what’s known, what’s missing, and what needs human review in stablecoin workflows.

[Roman M @treasdesk]

@danieldwalton The “locked out of the funnel” line is the key. Different format, different buyer psychology.

[Roman M @treasdesk]

@danieldwalton That review ecosystem point is sharp. Most people treat reviews as proof, not as part of the growth loop.