HiveXplore
A Hive blockchain social client, built in 36 hours.
A hackathon build for IIT Delhi CodeHive: a social client that reads posts, profiles and wallet history straight off the Hive blockchain and broadcasts new posts back to it. It is here as evidence of working against a chain rather than as a product.
Built with
Highlights
- ▸Signs users in through Hive Keychain or a HiveSigner OAuth2 redirect, so the app never sees a private key.
- ▸Reads live chain data through condenser_api and the dbuzz API — profiles, feeds, trending, wallet balances and transaction history.
- ▸Broadcasts posts and comments to the blockchain from the browser, where they persist independently of the app.
Where the data lives
Nothing a user writes is stored by this app. Posts and comments are signed in the browser by Hive Keychain and broadcast straight to the chain, so they outlive the deployment and stay readable by every other Hive client.
Reads go the same way round. Profiles come from condenser_api.get_accounts, the feed and trending lists from the dbuzz API, and wallet balances and transaction history from the account history call. The local SQLite database holds only session and preference data — losing it costs a user their theme, not their content.
Signing in without holding a key
- ▸Hive Keychain: the browser extension signs the challenge and the app only ever sees the signature.
- ▸HiveSigner: a full OAuth2 exchange — authorise, token, refresh, revoke — for people without the extension.
- ▸HiveAuth: request and QR generation are in place, but token verification is still stubbed, so it is scaffolding rather than a third working path.
- ▸A demo account covers judges and first-time visitors who have no Hive account at all.