- This Dapp UI & core features are inspired by awesome tutorial from Solana guys' tutorial
- Thanks to valuable advices from my advisor & co-workers who help shape the production of this project within limited hackathon timeframe
- Thanks to the awesomeness of Solana blockchain & its documentation
It takes advantages of Solana fast transaction speed to make (nearly) realtime fiat virtual card issuance come true. Having said that, Solana in specific, is helping the whole Blochain ecosystem moving forward with more practical & useful application.
| Responsive | Desktop |
|---|---|
 |
 |
This is a Next.js project bootstrapped with create-next-app.
The responsive version for wallets and wallet adapter may not function or work as expected for mobile based on plugin and wallet compatibility. For more code examples and implementations please visit the Solana Cookbook
npm install
# or
yarn installNext, run the development server:
npm run dev
# or
yarn devOpen http://localhost:3000 with your browser to see the result.
You can start editing the page by modifying pages/index.tsx. The page auto-updates as you edit the file.
API routes can be accessed on http://localhost:3000/api/hello. This endpoint can be edited in pages/api/hello.ts.
The pages/api directory is mapped to /api/*. Files in this directory are treated as API routes instead of React pages.
This Solana-fiat dApp wallet has these following features:
Wallet Integration with Auto Connec / Refresh
Web3 Js: Examples of one or more uses of web3 js including a transaction with a connection provider
Notifications (optional): Example of using a notification system
It is based on Next js Scaffold and proactively expanded with exchanger & virtual card issuance script folders.
├── public : publically hosted files
├── src : primary code folders and files
│ ├── components : should house anything considered a resuable UI component
│ ├── contexts` : any context considered reusable and useuful to many compoennts that can be passed down through a component tree
│ ├── hooks` : any functions that let you 'hook' into react state or lifecycle features from function components
│ ├── models` : any data structure that may be reused throughout the project
│ ├── pages` : the pages that host meta data and the intended `View` for the page
│ ├── stores` : stores used in state management
│ ├── styles` : contain any global and reusable styles
│ ├── utils` : any other functionality considered reusable code that can be referenced
│ ├── views` : contains the actual views of the project that include the main content and components within
style, package, configuration, and other project files
Anyone is welcome to create an issue to build, discuss or request a new feature or update to the existing code base. Please keep in mind the following when submitting an issue. We consider merging high value features that may be utilized by the majority of scaffold users. If this is not a common feature or fix, consider adding it to the component library or cookbook. Please refer to the project's architecture and style when contributing.
If submitting a feature, please reference the project structure shown above and try to follow the overall architecture and style presented in the existing scaffold.
To choose a task or make your own, do the following:
- Add an issue for the task and assign it to yourself or comment on the issue
- Make a draft PR referencing the issue.
The general flow for making a contribution:
- Fork the repo on GitHub
- Clone the project to your own machine
- Commit changes to your own branch
- Push your work back up to your fork
- Submit a Pull request so that we can review your changes
NOTE: Be sure to merge the latest from "upstream" before making a pull request!
You can find tasks on the project board or create an issue and assign it to yourself.