-
Notifications
You must be signed in to change notification settings - Fork 42
FAQ
I can’t get over the IPFS service in the welcome screen. AKASHA synchronises with Ethereum but IPFS can’t start, so I’m blocked.
After closing the AKASHA dapp, try to open "Activity Monitory" or "Task Manager" (depending on your OS) and search for IPFS.
If the IPFS process is still in the list please force quit it and then restart the AKASHA dapp.
In most cases this should fix it :)
You can find the Ethereum Identity Key(s) associated with your profile here:
On Windows C:/Users/%Your username%/AppData/Roaming/Ethereum/akasha-alpha/keystore
On Linux ~/.ethereum/akasha-alpha/keystore
On Mac ~/Users/%Your Username%/Library/Ethereum/akasha-alpha/keystore
If you want to port your identity on another computer, simply copy the Ethereum Identity Key in the corresponding directories described above. If things went smoothly, you should see your identity in the login screen the next time you start AKASHA.
With the -- fast option enabled, the chainsize is currently around ~200 Mb and it takes ~2-5 minutes to fully sync depending on your Internet connection and HDD.
The AKASHA chaindata is located here:
On Windows C:/Users/%Your username%/AppData/Roaming/Ethereum/akasha-alpha/geth/chaindata
On Linux ~/.ethereum/akasha-alpha/geth/chaindata
On Mac ~/Users/%Your Username%/Library/Ethereum/akasha-alpha/geth/chaindata
First of all, thank you for testing our dapp! As a pioneer, you just stumbled upon a hidden bug!
Please make a screenshot of the red screen containing the error and open an issue describing how we can reproduce the error.
The logs are located in the AKASHA/logs folder
%APPDATA% on Windows
$XDG_CONFIG_HOME or ~/.config on Linux
~/Library/Application Support on macOS
AETH is the test token we are using on our Ethereum test network. It does not have any value outside the purpose of testing the AKASHA dapp.
You receive AETH when you create an identity on AKASHA.