Skip to content

v0.1

Pre-release
Pre-release
Compare
Choose a tag to compare
@sontol sontol released this 05 Jul 06:30
· 2 commits to master since this release

This is first and final version of RingToken's Client. Usage Note:

  1. Run geth or any of your favorite flavor of Ethereum client with rpc enabled. I have already uploaded the contract into testnet. Example for geth: geth --rpc --networkid 2 --testnet console. You need the console because you are going to need to manually unlock your account everytime you are transferring both ether and the token.
  2. Run nw inside one of the client folder to start your client. I used nwjs v0.12.3 because I found that version is the least problematic
  3. Mint transfer ether to the contract, Mix uses ring signature to transfer the ether within the contract, Transfer Out transfer ether to outside account, contract is not supported.
  4. The client needs to be kept running if you are expecting payment or sending one, at least wait for 1 confirmation
  5. You can find your Ax,Ay,Bx,By inside the keychain.txt. They are the 2nd,3rd,5th, and 6th part of the file that starts with 0x. Ideally this file should be encrypted
  6. When you switch between client you will need to synchronize the pubkeys, privkeys, and keychain.txt file. For example after you finished running Mint you need to copy pubkeys, privkeys, and keychain.txt file into Mix folder before you use Mix. You will probably need to delete the previous existing pubkeys and privkeys folder inside the Mix before you copy them. Keychain.txt only need to be copied once
  7. Windows has 260 folder character limit so you need to extract the zip file into root folder because some of the node_modules folder goes pretty deep.
  8. No Mac release, I don't have budget for it :)
  9. Release was tested with Windows 8.1 and Ubuntu 14.04. It should be working for other flavors but I'm not sure of it.
  10. You will need to unlock your account manually every time you are making transaction. If you using geth you can do "personal.unlockAccount(eth.accounts[0],"yourpasswordhere")
  11. By default the client will use eth.accounts[0] to provide gas and ether. There is a possibility that this will lead to deanonymization if you don't use it carefully because you can see the "puppeteer's hand". I was thinking to use eth.accounts[0] for Mint and eth.accounts[1] for Mix and Transfer Out. I'm not sure how reliable this is though. Another option is to use exchange's hot wallet to provide gas if they support having variable amount of gas and data.
  12. One more thing, Ubuntu client requires libboostrandom1.55.0 so you need to install them through apt

As you can see the client is not that user friendly yet but this is where I leave you.