List view
- No due date•14/14 issues closed
- No due date
- No due date•32/32 issues closed
We will need to provide documentation for developers wishing to integrate Firefly into their own software. Initially the docs will just contain information around deep links, however more comprehensive integrations will follow.
No due date- No due date•21/21 issues closed
- No due date•30/30 issues closed
- No due date•15/15 issues closed
Firefly needs to show the different new assets, once it supports multiple networks. The idea is to flatten all assets regardless from which L2 Chain they are coming from. This milestone concerns itself with interaction across multiple chains and ERC-20/ERC-721 support.
No due dateDynamically supporting dapps will really allow us to interact and become a player within the web3 space.
No due dateThis includes basic support for L2 assets, differentiating between chains, flattening all assets from all chains, etc.
No due date•55/55 issues closedThis milestone handles the connection to a WASP node and access information about different EVM Chains.
No due date•77/77 issues closed- No due date•10/10 issues closed
- No due date•24/24 issues closed
- No due date•13/13 issues closed
- No due date•23/23 issues closed
Native mobile NFT media caching, improved settings
No due dateImplement UI and non-media technical aspects of the new Collectibles tab, including basic NFT media support & peripheral NFT functionality (basic media download)
No due date•7/7 issues closed- No due date•63/63 issues closed
This milestone aims to separate the logic within `packages/shared` and moving platform-specific logic into its respective platform folder.
No due date•30/30 issues closed- No due date•29/29 issues closed
Wallet.rs mobile implementation
No due date•35/35 issues closedIntegrate NFT media support into Firefly and implement peripheral NFT functionality.
No due date•30/30 issues closedImplement UI and non-media technical aspects of the new Collectibles tab.
No due date•38/38 issues closedAdd basic NFT functionality for sending and receiving / claiming NFTs in the wallet tab.
No due date•44/44 issues closedBaseline support for dynamic Governance events.
No due date•118/118 issues closed- No due date•25/25 issues closed
- No due date•29/29 issues closed
- No due date•70/70 issues closed
- No due date•32/32 issues closed
- No due date•10/10 issues closed
- No due date•201/201 issues closed
- No due date
TBD
No due date•4/4 issues closed- No due date
- No due date•86/86 issues closed
- No due date•46/46 issues closed
- No due date•19/19 issues closed
Support the use of Native NFTs on post stardust networks. Give users the space to view and share there NFTs with other people. Support the most popular NFT data standards and file types.
No due date•11/11 issues closedAllow users to view their native tokens, as well as useful information such as token price, and 3rd party details. Allow users to manage their native tokens, so they have control over them, and the storage deposit attached.
No due date•44/44 issues closedCreate a single FF application that can connect to both Shimmer and IOTA type networks. Create a simple and efficient development experience for adding features to Shimmer profiles, as well as upgrading IOTA profiles with those features at a later date. Simplify the UX of the Shimmer profiles by using one single address per account. Improve the user onboarding experience, so that the user can create a profile and connect to the right network with minimal learning curve.
No due date•93/93 issues closedSince we will be after all developing a tool to interact with web3, it is imperative that we understand as much as we can about the space and how to properly build software for it.
No due date•3/3 issues closedIt is quite important to have significant test coverage, both for integration and unit tests. At the moment, much of our code is untested :see_no_evil:.
No due date•9/9 issues closedTo improve overall developer experience (esp. onboarding and resources), we will create a Firefly handbook. This is a simple static website purely for hosting documentation. It will live closely to the repository to make it easier to find and update the information.
No due date•10/10 issues closed- No due date•64/64 issues closed
To enable the wallet to send the network token on post stardust networks, i.e., SMR token on Shimmer. To support the core feature blocks that can be added to a transaction in the new extended UTXO. To improve the UX of sending and receiving a transaction. To allow the user to efficiently send micro-transactions and safely send large value transactions. To enable the management of tokens locked as storage deposit. To ensure old flows have similar UX improvements and aesthetics.
No due date•151/151 issues closed- No due date•30/30 issues closed
- No due date•121/121 issues closed
The milestone for the second phase of Firefly's shared library refactor. See more [here](https://hackmd.io/4VBXE7u7RyeD9kgjPV3tgQ).
No due date•11/11 issues closedThe initial phase of Firefly's shared library refactor. See more [here](https://hackmd.io/FpiM5-uWSGavKfFY89omxw).
No due date•6/6 issues closedSimplify current and future technical implementation for hierarchical deterministic wallets in FF. Simply user experience and make easier the use of hierarchical determinstic wallets in FF. Prepare navigation structure for future features and concepts coming to FF, to support stardust upgrade of IOTA mainnet and introduction of shimmer network. Clean up organisation of existing features, so that tabs only have content belonging to their context, and profile specific features are at a profile level.
No due date•84/84 issues closed