Skip to content

QuantumMechanics/XEMsign

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

XEMsign

Automated cosignature for XEM Cryptocurrency

Features

  • Password encrypted configuration (aes-128-ecb)
  • Batch signatures
  • Timer
  • Max amount per tx, program stops if amount exceeded (meaning something goes wrong)
  • Max dayli amount
  • Transaction details

How to

You must have a local NCC running connected to a local or remote NIS.
If you want it to be as light as possible, you can use a local NCC to sign the multisig transactions and a remote NIS to propagate them. The cosignatory account needs to be in a wallet that belongs to your local NCC.

To connect your NCC to a remote NIS:
-Run the NCC only
-In settings choose Remote Server and enter the Host (you can choose an host here)
-Save. Now you can close your browser and let the NCC run in background.

You need NodeJs.
Be sure you have NEM.js from nodejs2nem inside your folder.

XEMsign check every n minutes for transactions initiated by XEMpay. The program signs transactions only if they meet requirements set in access.json

You need to insert correct informations inside access.json:
All addresses must be in the "NAMOAVHFVPJ6FP32YP2GCM64WSRMKXA5KKYWWHPY" format. NO "-".

  • Wallet & transaction informations (Warning, for "fee" only, value is in the smallest possible NEM fraction, that means that 1000000 means 1.000000 NEM).
  • timer: Number of minutes between each pull, set by default to 5 (1 cause the resignature of the same transaction because it has no time to get confirmed).
  • dayliTimer: Timer before dayliAmount reset to 0 in minutes
  • maxAmount: Maximal XEM amount per tx, in case of a bigger transaction, the program stop.
  • maxDayliAmount: Maximal amount per days.

Next, Run XEMsign.js using:

nodejs pathTo/XEMsign.js

Then follow instructions.

Not working ?

Normally it should work out of the box. If not, you need to check:

  • If NEM.js is present in your folder
  • If you have deleted access.json after encryption.

If still not working, you need to install Express and Secure-conf:

  • Express: npm install express
  • Secure-conf: npm install secure-conf

Warning

As the wallet is exposed you shouldn't store any funds on it !

To insure maximum security, you can deploy as many XEMsign as you need cosignatures but preferably on different computers in different locations. And do not use those computers for surfing the net.

Work in progress

  • Fill access.json with random datas and auto delete.

BTC: 1BRuxYZ3ohDJkfEWKVMWAiYrAYjwNSaPJs
XEM: NAMOAV-HFVPJ6-FP32YP-2GCM64-WSRMKX-A5KKYW-WHPY

About

Automated cosignature for XEM Cryptocurrency

Resources

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published