While working through a simple shielded transaction setup in the CreatorPad task on Midnight Network, $NIGHT , #night , @MidnightNetwork , what caught me off guard was how the default path still leans heavily on developer-configured selective disclosure rather than handing granular control straight to the end user during basic interactions. I expected more immediate, user-facing toggles for what gets revealed—something like a quick checkbox for sharing proof-of-age without extras—but the flow kept routing through the application's pre-set shielding logic, where the user essentially trusts the dApp builder's choices upfront. One concrete thing: even in test mode, attempting a minimal data reveal required approving a developer-defined access key structure first, not a spontaneous user decision mid-flow. It makes sense for compliance and sanity in complex apps, yet it quietly shifts the real control point earlier, to whoever codes the contract. I keep wondering if that early embedding of decisions will actually reduce user burden over time or just relocate the trust assumption to a different layer.