
Creation of new asset on Statemine for a user who had no prior interactions with this chain is a relatively complex process. Similarly, when doing assets transfers on Statemine, several factors need to be considered to make it successful.

We propose to develop user interfaces, which would create great UX for both processes.

### Team:
We're [Ethworks](https://ethworks.io/), a blockchain software-house. For the Polkadot/Kusama community, we've implemented the [Bounties UI](https://kusama.polkassembly.io/bounty/0) and worked on 2 other UI-related grants: [1](https://github.com/w3f/General-Grants-Program/blob/master/grants/speculative/polkadot_js_chrome_extension.md), [2](https://github.com/w3f/Grants-Program/blob/master/applications/polkadot-desktop-app.md).

### Details:
You can find all the relevant proposal details [in this doc](https://docs.google.com/document/d/1xHGKG0k6slVxQBMsbZzIZiWXVqj7IMJh4uJ1mEUaELM/edit?usp=sharing)

[Figma wireframes](https://www.figma.com/file/NkmjWg3KVaXz0ByIVbJPY0/Statemine-wireframes?node-id=0%3A1)

Treasury Proposal: UIs for easier creation of assets on Statemine and asset transfers

There should be an easy way to utilize tokens that “live” on Statemine from other parachains. At the moment, this is not easily achievable. The go-to solution would be to teleport assets to other chains, thus replicating the state and losing the benefits of chain specialization.

A runtime-level parachain app can send an XCMP transfer message to Statemine, but currently has no way of reading Statemine's state, or have a secure execution confirmation.

We'd like to explore other possible options to achieve integration of a parachain dApp with Statemine.

1. The dApp connects to both app parachain and Statemine, performing app logic on the first and asset transfers on the other
2. The dApp lives in an off-chain worker on the parachain. It connects to Statemine as part of business logic execution.
3. The dApp lives in the runtime/smart contract. Off-chain worker synchronises part of the state from Statemine to the parachain to.

We'd like to create a PoC app for each solution. Where applicable, we'd extract APIs to allow developers for easier use of our results.

As it's a bit exploratory/research proposal, we may end up implementing some better ways of using assets cross-chain, if we find them.

### Team:
We're [Ethworks](https://ethworks.io/), a blockchain software-house. For the Polkadot/Kusama community, we've implemented the [Bounties UI](https://kusama.polkassembly.io/bounty/0) and worked on 2 other UI-related grants: [1](https://github.com/w3f/General-Grants-Program/blob/master/grants/speculative/polkadot_js_chrome_extension.md), [2](https://github.com/w3f/Grants-Program/blob/master/applications/polkadot-desktop-app.md).

### Details:
You can find all the relevant proposal details [in this doc](https://docs.google.com/document/d/1cOilg94kimMn9hWw2vp0YR8AwlHzLjoHc-k4mlDSEMg/edit#).

Treasury Proposal: Streamline use of Statemine Assets in dApps on other parachains

This proposal is for the first deliverable of [Treasury Proposal: UIs for easier creation of assets on Statemine and asset transfers](https://kusama.polkassembly.io/post/802).

The deliverable is to create a cross-chain user interface for asset creation and includes:

- Standalone user interface (incl. hosting and DNS setup)
- Read relay chain balance
- Read Statemine balance for selected asset and KSM
- “Create asset” UI
- Checks for required balances on Kusama and Statemine
- List all required transactions (incl. cross-chain transfers)
- Execution of all required transaction
- Reporting transactions progress to the user

For additional details, please refer to the [main post](https://kusama.polkassembly.io/post/802), [the doc](https://docs.google.com/document/d/1xHGKG0k6slVxQBMsbZzIZiWXVqj7IMJh4uJ1mEUaELM/edit#l) and [the wireframes](https://www.figma.com/file/NkmjWg3KVaXz0ByIVbJPY0/Statemine-wireframes?node-id=0%3A1).

Update: Here are [the designs in Figma](https://www.figma.com/file/oOjQbcG96IpVoV2X9yZM5G/Statemine-design-and-components?node-id=506%3A1). Happy to hear your feedback!

No tip found