https://alpha-testnet-gwen.liftedinit.tech/

Firefox 111.0
Manjaro Linux

1. Create a new token using the token identity
2. After clicking the "Create Token" button, the page refreshes and displays the token creation dialog again.

I would expect to see the token list after creating a new token.

See liftedinit/alberto#135

@stanleyjones

Description: Only the Token Authority is able to mint/burn at the moment. Allow a token owner to mint/burn the token via UI.

Relates to liftedinit/many-rs#372

As a token owner, I want to be able to mint/burn my token via a UI so that it is easy to manage.

• Should be able to mint/burn tokens as a token owner via Gwen.
• Should NOT be able to mint/burn tokens if not a token owner.
• Should be demoed.

See #55 (comment)

1. Write a value to the kvstore using some identity

$ kvstore --pem id2.pem https://alpha-testnet.liftedinit.tech/api/kvstore put mykey somevalue

2. Verify the value has been written

$ kvstore https://alpha-testnet.liftedinit.tech/api/kvstore get mykey
somevalue%

3. Open Gwen. Make sure the KVSTORE endpoint is correct
   

4. Notice that the new KV pair is not listed in the UI
   

We are still on 16.10, causing an issue with some Web3Auth nested dependencies.

At the moment of writing these lines, only the Token Authority can create new tokens.

Gwen hardcodes the destination address, i.e., the destination where the new tokens will be allocated, to the address of the user creating the token, which is always the token authority.

It would be great if the address were not hardcoded to simplify the Alpha Cohort onboarding documents.

One is stuck in an infinite loop when creating a new HSM account. The same is happening when importing said HSM account and displaying the Ledger info.

@stanleyjones

One can create/import a hardware authenticator MANY identity when using a kvstore backend. The application should not display the option to the user as the kvstore backend does not currently support hardware authenticator.

When a new token is created, the list of tokens available should refresh.

Make Gwen on par with the backend

• Token creation
• Token update
• Add extended info
• Remove extended info
• Token info (summary, supply, owner, ...)

It would also be great to track the history of the modifications made to a token, in the same fashion we're following the history of MFX in Alberto for each user.

When creating a new token, the operation appears successful but the console reports an unauthorized Token user.

If the user is authorized (i.e. id1) then everything works as expected.

Not sure if this is a real issue as I am a complete web UI newbie, but it seems that some UI ids, e.g., id=tabs-21--tab-1, change from tab to tab.

I am using UI.Vision RPA to generate screenshots for the onboarding documentation, and the tool needs a non-changing name/id otherwise, the macro cannot replay correctly.

Is assigning a non-changing name/id to all UI components possible?

Also affects Alberto.

https://alpha-testnet-gwen.liftedinit.tech

Log in as the Token Authority and try creating a new token whose Name contains spaces or numbers.

Add support for code coverage and add a code coverage badge in the README.

https://alpha-testnet-gwen.liftedinit.tech

Firefox 111.0
Manjaro Linux

To reproduce, click on the "Update account" button

Notice the MANY address is overflowing