This dApp runs on LUKSO network. It allows to:
- browse Universal Profiles (UP)
- see UP associated assets (tokens and NFTs) and profile metadata
- see network activity
- connect and send assets
- buy native LYX token on LUKSO network
This project is deployed via Cloudflare pages.
When you create a PR, a preview URL will be appended to the PR discussion.
Branch: main
App supports data fetching through RPC or using GraphQL indexer. By default it uses Graph mode but can be changed from user settings.
RPC mode is more up-to-date but this comes at the cost of loading speed. It also limits amount of available features that are not possible in this mode.
It is possible to pass a network in query parameter to force viewing a profile on a given network:
?network=testnet
?network=mainnet
At runtime we look at the Local Storage "debug" key to show various logs. The following log streams are available:
dapp:asset
-> Show asset objectsdapp:token
-> Show token objectsdapp:profile
-> Show profile objectsdapp:generic
-> Generic logsdapp:send
-> Send logsdapp:graph
-> GraphQL logstanstack:query
-> Show how queries as postedtanstack:results
-> Show results of queries
You can use * for any section or all. For example:
debug=\*
debug=dapp:\*,tanstack:query
debug=dapp:,tanstack:
Use the Chrome debugger to add it to LocalStorage for the dApp site URL.
Install packages:
yarn install
Run the development server:
yarn dev
Check the code:
yarn lint
yarn test
Preview the production build:
yarn preview
App use Yata, a third party website for managing translations. Do not edit json
files for translations manually as they will be overwritten when fetching from Yata.
Please first set
YATA_API_TOKEN
as an environment variable or locally in the root folder.env
file (see.env.example
).
For generating translations use following script:
yarn yata-fetch
Using local tools-web-components
This repo will look for ../tools-web-components/package
to turn on linking.
To link please run
yarn link -p ../tools-web-components/package
To unlink please run
yarn unlink ../tools-web-components/package
Make sure you remove link before pushing, otherwise it won't build in Cloudflare.
We use single branch flow. Just merge your feature PR into main
branch and new release will be triggered.