aeternity / ae-token-minter

Aeternity node

A new blockchain for æpps.

Optimized for scalability via smart contracts inside state-channels.

Has a built-in oracle for integration with real-world data.

Comes with a naming system, for developerability.

Written in Erlang.

To install and run the Aeternity node, see the instructions below or just follow the progress of the project via GitHub Issues.

If you have discovered a bug or security vulnerability please get in touch. The Aeternity Crypto Foundation pays bug bounties up to 100.000 AE Tokens for critical vulnerabilities. Please get in touch via [email protected].

Documentation

For an overview of the installation process for different platforms, building the package from source, configuration and operation of the Aeternity node please refer to Aeternity node documentation.

We keep our protocol, APIs and research spec in separate protocol repository.

How to start

We publish packages for major platforms on GitHub. Each release comes with release notes describing the changes of the Aeternity node in each particular version.

Please use the latest published stable release rather than the master branch. The master branch tracks the ongoing efforts towards the next stable release to be published though it is not guaranteed to be stable.

Quick Install

Linux / Mac

By using the installer to install the latest stable version:

bash <(curl -s https://install.aeternity.io/install.sh)

See the documentation for starting and configuring the node.

Docker

Alternatively, you can run the node client as a docker container:

Linux / Mac

Or running a docker container (latest tag):

mkdir -p ~/.aeternity/maindb
docker pull aeternity/aeternity
docker run -p 3013:3013 -p 3015:3015 \
    -v ~/.aeternity/maindb:/home/aeternity/node/data/mnesia \
    aeternity/aeternity

Windows

mkdir %APPDATA%\aeternity\maindb
docker pull aeternity/aeternity
docker run -p 3013:3013 -p 3015:3015 -v %APPDATA%/aeternity/maindb:/home/aeternity/node/data/mnesia aeternity/aeternity

Restore from snapshot

To speed up the initial blockchain synchronization the node database can be restored from a snapshot following the below steps:

• delete the contents of the database if the node has been started already
• download the database snapshot
• verify if the snapshot checksum matches the downloaded file
• unarchive the database snapshot

Note that the docker container must be stopped before replacing the database

The following snippet can be used to replace the current database with the latest mainnet snapshot assuming the database path is ~/.aeternity/maindb:

rm -rf ~/.aeternity/maindb/ && mkdir -p ~/.aeternity/maindb/
curl -o ~/.aeternity/mnesia_main_v-1_latest.tar.zst https://aeternity-database-backups.s3.eu-central-1.amazonaws.com/main_backup_v1_full_latest.tar.zst
CHECKSUM=$(curl https://aeternity-database-backups.s3.eu-central-1.amazonaws.com/main_backup_v1_full_latest.tar.zst.md5)
diff -qs <(echo $CHECKSUM) <(openssl md5 -r ~/.aeternity/mnesia_main_v-1_latest.tar.zst | awk '{ print $1; }')
test $? -eq 0 && tar --use-compress-program=unzstd -xf ~/.aeternity/mnesia_main_v-1_latest.tar.zst -C ~/.aeternity/maindb/

Additional resources

• Threat Model

ae-token-minter's Issues

Inconsistency in mandatory hint pop up

Issue type

I'm submitting a ... (check one with "x")

• bug report
• feature request
• question about the decisions made in the repository

Issue description

Current behavior:
Not all text fields do have a mandatory field description pop up.
Added screen shows the mandatory text pop up for Token creation screen

Expected behavior:
Add missing mandatory field text to fields on mint NFT page.

Steps to reproduce:
Open https://docs.aeternity.com/ae-token-minter/nft/mint
Click in field Name
Click in field Symbol
Verify that a mandatory input text does not appear for field Name :)

Related code:

insert short code snippets here

Other information:

npm, node, OS, Browser

<!--
Node, npm: `node --version` and `npm --version`
OS: Windows (7/8/10). Linux (incl. distribution). macOS (El Capitan? Sierra?)
Browser: Chrome/Safari/Firefox/etc?
-->

Angular, Nebular

<!--
Check your `package-lock.json` or locate a `package.json` in the `node_modules` folder.
-->

Code preview is broken in Firefox browser

Issue type

I'm submitting a ... (check one with "x")

• [x ] bug report
• feature request
• question about the decisions made in the repository

Issue description

Current behavior:
Code preview is broken in Firefox browser when I'm minting token.

Expected behavior:
Should be visible.

Steps to reproduce:

1. Open minter in FF browser
2. Click on Tokens
3. Check Code preview

Inconsistency in full stops in help text

Issue type

I'm submitting a ... (check one with "x")

• bug report
• feature request
• question about the decisions made in the repository

Issue description

Current behavior:
The help text and the mandatory info text have an inconsistency in full stops at the end of the sentence. Some text does have and other don't have a full stop.

Expected behavior:
Consistency :)

Steps to reproduce:

Related code:

insert short code snippets here

Other information:

npm, node, OS, Browser

<!--
Node, npm: `node --version` and `npm --version`
OS: Windows (7/8/10). Linux (incl. distribution). macOS (El Capitan? Sierra?)
Browser: Chrome/Safari/Firefox/etc?
-->

Angular, Nebular

<!--
Check your `package-lock.json` or locate a `package.json` in the `node_modules` folder.
-->

Create Token button is disabled

Issue type

I'm submitting a ... (check one with "x")

• bug report
• feature request
• question about the decisions made in the repository

Issue description

Current behavior:
After rejecting the token creation, the CREAT TOKEN button is disabled

Expected behavior:
After rejecting the token creation, the user should be able to modify the entered values and hit the CREATE TOKEN button again

Steps to reproduce:
Go to : https://docs.aeternity.com/ae-token-minter/token/create
enter all necessary information to create a Token
Hit the CREATE TOKEN button
on the appearing window select the REJECT button
User is back on the create page, but the CREATE TOKEN button is disabled

Related code:

insert short code snippets here

Other information:

npm, node, OS, Browser

Browser: Brave Version 1.47.186 Chromium: 109.0.5414.119 

**Angular, Nebular**

Add info about Network

Hey,
I'm submitting a feature request.

• bug report
• [ x] feature request
• question about the decisions made in the repository

###Description

Current behavior:
Currently, it's not clear what network is used by minter , there is no info on the page. To do something I should try it in both networks.

Expected behavior:
I would like to see what network is used by minter.
Maybe will be useful to add this info.

Steps to reproduce:

Related code:

insert short code snippets here

Other information:

npm, node, OS, Browser

<!--
Node, npm: `node --version` and `npm --version`
OS: Windows (7/8/10). Linux (incl. distribution). macOS (El Capitan? Sierra?)
Browser: Chrome/Safari/Firefox/etc?
-->

Angular, Nebular

<!--
Check your `package-lock.json` or locate a `package.json` in the `node_modules` folder.
-->

User info after creating a token

Issue type

I'm submitting a ... (check one with "x")

• bug report
• feature request
• question about the decisions made in the repository

Issue description

Current behavior:
After the token has been created, the user is advised to check the token in his wallet, but the token will not appear just after the creation. This could be misleading for the user as she/he doesn't see it in the wallet.

Expected behavior:
As the user gets a nice info pop up as she/he clicks on the View button after creating a token, it could be written that it will take a view minutes for the token to appear in the wallet.

Steps to reproduce:
Create a token and check your wallet just after.

Related code:

insert short code snippets here

Other information:

npm, node, OS, Browser

<!--
Node, npm: `node --version` and `npm --version`
OS: Windows (7/8/10). Linux (incl. distribution). macOS (El Capitan? Sierra?)
Browser: Chrome/Safari/Firefox/etc?
-->

Angular, Nebular

<!--
Check your `package-lock.json` or locate a `package.json` in the `node_modules` folder.
-->

Mandatory fields highlighting is inconsistent

Issue type

I'm submitting a ... (check one with "x")

• bug report
• feature request
• question about the decisions made in the repository

Issue description

Current behavior:
Some fields are highlighted when the mouse moves to another field, some field are highlighted when user focus on other field

Expected behavior:
Highlighting should be consistent throw the page

Steps to reproduce:
See link for demo video of the issue
https://www.loom.com/share/25ac1df4974d4211b296ea53c0a54908

Related code:

insert short code snippets here

Other information:

npm, node, OS, Browser

<!--
OS: Windows (10)
Browser: Brave
-->

Angular, Nebular

<!--
Check your `package-lock.json` or locate a `package.json` in the `node_modules` folder.
-->

Testnet Mode

Issue type

I'm submitting a ...

• bug report
• feature request
• question about the decisions made in the repository

Issue description

Current behavior:
Can't seem to connect wallet set to testnet.

Expected behavior:
Allow testnet usage.

Steps to reproduce:
Set superhero wallet to testnet, try to connect/mint token.