Sometimes I send the whole statement when they only needed the address. I tell myself I'll crop it later. I never do. The extra fields just sit there in the attachment.

Most processes are built to accept it.

I started looking at Citadel on Dusk because I couldn't tell who is actually allowed to ask the question. The pitch is regulated finance on-chain, which I kept reading as: keep the market private, still let someone check eligibility. Those two were fighting in my head for a bit.

The flow is slower than the sentence. You go to a license provider, they check you off-chain, they sign some attributes, they register an encrypted license. Then later you prove you hold one without showing which one. I thought the contract was the yes. It verifies the proof and writes a session. Access is a different step. The service provider takes a cookie and decides on its own.

I'm still getting used to that split. The chain can confirm a license without anyone else seeing who. Someone specific can still look and say yes or no. That might be the whole thesis.

It does mean the session is doing more than I first gave it credit for. I'm not sure whether the hard part is hiding which license, or how far the session can reopen before it looks like the file again.

#dusk $DUSK @Dusk $BTC