Skip to content

User interfaces provider interface#16

Open
mudigal wants to merge 6 commits intofeat/file-systemfrom
user_interfaces_provider_interface
Open

User interfaces provider interface#16
mudigal wants to merge 6 commits intofeat/file-systemfrom
user_interfaces_provider_interface

Conversation

@mudigal
Copy link
Collaborator

@mudigal mudigal commented Feb 23, 2026

User Interfaces Layer

  • provider interface

Add initial provider dashboard with React 19, Vite 6, Tailwind CSS 4,
and RxJS state management. Includes pages for overview, registration,
agreements, checkpoints, challenges, and earnings.
- Add chain-client library for direct blockchain interaction via WebSocket
- Update chain state to use real WebSocket connection
- Add registration status check when wallet connects
- Create multi-step registration wizard for new providers:
  - Connect wallet and blockchain
  - Set stake amount with validation
  - Configure provider settings
  - Review and confirm registration
  - Success page with next steps
- Show settings management UI for already-registered providers

New providers can now register directly from the dashboard without
needing a provider node running first.
…ress

Replace polkadot-api's unsafeApi with @polkadot/api for transaction
submission. The unsafeApi had issues encoding complex struct types
causing "Cannot read properties of undefined" errors.

Changes:
- Add @polkadot/api alongside polkadot-api (queries still use polkadot-api)
- Create dev account signer using @polkadot/keyring for local development
- Add progress callbacks to transaction functions for UI feedback
- Update Registration page to show transaction status messages
- Fix transaction finalization by using isInBlock for faster response
@bkontur
Copy link
Collaborator

bkontur commented Feb 26, 2026

@mudigal I've not tried it yet, I will, but user-interface-layer/provider-dashboard what about just ui/provider-dashboard or maybe just ui/provider. I mean just nit user-interface-layer, everybody understand would understand ui is unnecessary and will generate long paths :), or maybe user-interface-layer -> frontend

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants