Hey everyone, I’ve been working on something called RODiT (Rich Online Digital Tokens) and would love to get feedback from the community.
The Problem: Traditional API authentication has some fundamental issues: You need to maintain user databases and session state. Mutual authentication (proving both client AND server identity) is rare. Webhooks are basically impossible to authenticate properly. Authentication, configuration, and licensing are three separate systems
What RODiT Does Differently: RODiT is a token that combines authentication, configuration, and subscription licensing into a single blockchain-anchored credential on NEAR Protocol. Here’s what makes it different:
Stateless Mutual Authentication: Both client and server continuously verify each other’s identity withou…
Hey everyone, I’ve been working on something called RODiT (Rich Online Digital Tokens) and would love to get feedback from the community.
The Problem: Traditional API authentication has some fundamental issues: You need to maintain user databases and session state. Mutual authentication (proving both client AND server identity) is rare. Webhooks are basically impossible to authenticate properly. Authentication, configuration, and licensing are three separate systems
What RODiT Does Differently: RODiT is a token that combines authentication, configuration, and subscription licensing into a single blockchain-anchored credential on NEAR Protocol. Here’s what makes it different:
Stateless Mutual Authentication: Both client and server continuously verify each other’s identity without maintaining backend sessions. The token itself contains all the permissions, rate limits, and configuration.
Local Key Generation: Keys are generated on endpoints themselves - no CSRs, no certificate authorities, no central key management. When you purchase a RODiT, it’s minted and sent directly to your NEAR blockchain address.
Continuous Validation: Unlike JWT tokens that are “fire and forget,” RODiT tokens are periodically re-validated during API calls, preventing token theft and replay attacks.
Built-in Commerce: Tokens can be resold, swapped, or white-labeled. Subscription management is built into the authentication itself.
Working Demo: I’ve built a live demo API called TimeHereNow that showcases the technology: timeherenow.com All time values are sourced from NEAR blockchain (polled at 5Hz) Full IANA timezone database integration Blockchain-timestamped webhook timers Complete NPM package for easy integration The demo is fully functional - you can actually purchase a RODiT token and start making authenticated API calls.
Technical Details: More info at discernible.io including whitepaper and API docs.
Looking for Feedback: I’m at the stage where the technology works and the demo is live, but I don’t have users or partners yet. I’m trying to figure out: Does this solve a problem you actually have? What use cases would you be most interested in? Would you prefer this as open source, proprietary, or hybrid?
I’m particularly curious about developers working with: API authentication and metering Webhook security IoT device provisioning VPN/secure networking Any regulated environments (finance, healthcare)
Happy to answer technical questions or discuss the architecture. Would genuinely appreciate any thoughts or criticism.
Note: This is blockchain as infrastructure, not crypto speculation - the NEAR blockchain is used purely for credential anchoring and verification.