Thursday, 11 May 2017

run masternodes under ubuntu command line

nerd level 6.
please ensure you have a working knowledge of masternode setup before attempting this.

refer to
http://bumbacoin.blogspot.com.au/2016/07/how-to-setup-exclusive-coin-master-node.html

...
i have pre-compiled the ubuntu daemon so it's a matter of fetching it,
setting up the .conf file, syncing it, setting up the masternode file and starting masternodes.

all files are available here
https://github.com/exclfork/ExclusiveCoin/releases/tag/v1.2.0.0-daemon

--
#get daemon from github
wget https://github.com/exclfork/ExclusiveCoin/releases/download/v1.2.0.0-daemon/exclusivecoind-ubuntu-v1200

#rename for ease of use
mv exclusivecoind-ubuntu-v1200 exclusivecoind

#change permissions so you can run the daemon
chmod +x exclusivecoind

#create and modify datadirectory and conf file, you need to be in home or ~ directory
cd
mkdir .exclusivecoin
touch .exclusivecoin/exclusivecoin.conf
nano .exclusivecoin/exclusivecoin.conf

### now you're in a text editor you want to add
rpcuser=yourusername
rpcpassowrd=fancypassword
daemon=1
rpcallowip=127.*.*.*:*
server=1
port=12345
genproclimit=-1


#then to quit
[ctrl]+x
Y
[enter]

#now you can start the daemon and let it sync
./exclusivecoind &

#create masternode
touch .exclusivecoin/masternode.conf
nano .exclusivecoin/masternode.conf

#you need to stop/restart the daemon to enable the masternode.conf
./exclusivecoind stop
./exclusivecoind &

#to check that you are synced
./exclusivecoind getinfo

#then compare blocks to height at https://www.cryptobe.com/chain/ExclusiveCoin

#assuming everything is synced and you're all in love
./exclusivecoind masternode start-many

#to ensure masternodes dont stop setup regular cron job which will continue sending prior command
crontab -e

#this may give you a choice of editor, choose nano.
#scroll/arrow down to the end of the file and enter this line
*/15 * * * * ~/exclusivecoind masternode start-many

[ctrl+x
Y
[enter]



#### for local control/access of coins

#any wallets that share private keys will share identical transactions,
#import all the privkeys into your local wallet

#also there is a bootstrap available here
http://cryptochainer.com/dir/?page_id=881



--
#handy daemon commands, the daemon is a command line version of the wallet,

#start daemon, the & symbol is necessary to free up the command line
./exclusivecoind &

#stop daemon
./exclusivecoind stop

#gives information regarding client and blockchain
./exclusivecoind getinfo

{
    "version" : "v1.2.0.0-61404",
    "protocolversion" : 61404,
    "walletversion" : 60000,
    "balance" : 0.00000000,
    "darksend_balance" : 0.00000000,
    "newmint" : 0.00000000,
    "stake" : 0.00000000,
    "blocks" : 26671,
    "timeoffset" : 0,
    "moneysupply" : 3674200.00000000,
    "connections" : 21,
    "proxy" : "",
    "ip" : "",
    "difficulty" : 1458.01970256,
    "testnet" : false,
    "keypoololdest" : 1494518106,
    "keypoolsize" : 1001,
    "paytxfee" : 0.00010000,
    "mininput" : 0.00000000,
    "errors" : ""
}

#start masternodes
./exclusivecoind masternode start-many


#to get list of possible commands
./exclusivecoind help



--
possible issues,
nano is a text editor, it might need to be installed
it's far more noob friendly than vim.

apt-get install nano


--
for OSX basically the process is similar,
but quite possibly default editor for crontab is already vim, so to open use

EDITOR=nano crontab -e

for ease of file location, drag/drop your coind from it's location onto the editor whilst editing,
my entry ended up as

*/15 * * * * * /Volumes/data/ExclusiveCoin/exclusivecoind-osx-v1200 masternode start-many

Saturday, 8 April 2017

simple way to restart masternodes in windows


this is going to be a quick and slightly messy post :) i'm not going in depth to how you do each step, so hopefully you can work it out or someone else can expand it (please also see other posts by myself on how to setup the masternode)
it uses the exclusivecoind.exe which is the command line wallet, no gui, so you send it rpc calls via the command line to interact with it.

a basic method to address the seeming issue where running multiple masternode with a single exclusivecoin instance is problematic, they stop after a while.

i use a workaround in linux where i setup a cronjob to restart them every 15 minutes.
the basic format is

*/15 * * * * * exclusivecoind masternode start-many


to replicate this in windows you need a couple basic steps, not to mention setting up yr actual masternodes.

1) you need the exclusivecoind.exe, download the following and you will find the coind in the releases folder, it is an older version but is still fully compatible with network
https://github.com/exclfork/ExclusiveCoin/archive/bfaea17a0fe24f801004b3cd8eee1bbe607f2cb8.zip
to run the coind the exclusivecoin.conf file will need 
rpcuser=yourusername
rpcpassword=youruserpassword
2) a bat file to run.
in the bat file, will be a simple loop to send a command to the exclusivecoind.exe

1- download the file, 
make sure you added rpcuser/rpcpassword to your .conf file
to run you will need a command prompt, cd to where file is located
start /b exclusivecoind.exe
using "start" means it will run in background so you can interface with it eg. exclusivecoind.exe getinfo
2- in a windows explorer navigate to where you want the bat file to run (mine is in same location as coind.exe),
right click > create new text file
rename to "whatever.bat"
right click file > edit
:loop
exclusivecoind.exe masternode start-many
timeout /t 900 /nobreak
goto :loop
open another command terminal, navigate to where the bat file is then start it.
whatever.bat

done.
now you can send rpc commands to the coind in the first command window while the second just loops until you close it.
if yr masternodes stop due to the "issue", then every 15 minutes (900 seconds) the command to start-many should kick them back into life.


you may find further discussion on it there.

if this helps, please consider donating :)
EXCL ER2Z8HqUKdpBDGbo4cgZfU9uvv2pAwVoxr

Monday, 6 March 2017

manage files download from developer.apple.com

Downloading large files from Apple sucks. Here's how to apparently download using terminal with resume option ....



How to download files from Apple Developer Center:

  1. Open Terminal
  2. run gem install adcdownload
  3. Open https://developer.apple.com/down... and copy the URL of a file.
  4. run adcdownload get http://adcdownload.apple.com/…/file.dmg
  5. You will be asked for your Apple ID and password.
  6. Your download should start. If your connection drops, re-run the same command to continue the download.

https://github.com/MagLoft/adcdownload


this information from 
https://www.quora.com/How-do-you-download-Xcode-without-the-App-Store

Saturday, 16 July 2016

How to setup an Exclusive Coin master node.


1. send 5000 EXCL to address,
2. modify exclusivecoin.conf ,
3. enter masternode details,
4. start master node.


There is at least one instance in the Qt that mentions sending 10,000 coins for master node, this is incorrect. You only need 5,000 (at the moment, this may change).


1.
go to new wallet and get new address, send exactly 5000 coins to that address, if you want two master nodes use two addresses etc ..


2.
here's my exclusivecoin.conf, i'm not sure exactly what is necessary but this works :)

rpcallowip=127.*.*.*:*
rpcuser=whatever(make something up)
rpcpassword=whatever(make something up)
server=1
daemon=1
listen=0

3.
you will need this data to create the masternode
alias address:port privkey txid position

alias is just a name for that master node, it can be anything
address:port is yr wallets ip and a port, each master node must have different ports
privkey is the privkey to the address you sent 5k to, each mn must have different address/privkeys
txid and position once you've sent the funds, go to console,

to get your address:port
in different versions of the code the process will involve either "getpeerinfo" or "getinfo"


go to debug console, the image below shows getpeerinfo, however for later clients use getinfo 
>getpeerinfo

look for "addrlocal" : "x.x.x.x:45912",  the x.x.x.x is yr address, then add a port, each master node needs unique port.
Exclusive Coin uses 23230 as a default port, I use something like 23235, 23236, 23237 etc for multiple master nodes.

if "addrlocal" is not reported then use
>getinfo

look for "ip" : "180.216.153.36",

IF your client only reports your IP as "0.0.0.0" use google and look up "whatsmyip".

privkey is the privkey to the address you sent 5k to, go to console,
>dumpprivkey enteryouraddresshere

txid and position once you've sent the funds, go to console,
>masternode outputs


4.
now go to master node tab in Qt, and press create, enter your details and press OK.

then press Update, and Start.















.
If God loves you then you will now have a running Masternode !!


In your data directory there is now a file called masternode.conf
It holds the data you entered when creating the node, it will look something like below.

alias address:port privkey txid position

If you have multiple nodes then each will have their own separate line of data.
Importantly, each seperate node needs seperate port, excl address, tx.

It's worth noting that "masternode outputs" will give a list in any order without any obvious linkage to address, you'll have to work out which tx goes with which address/privkey




Exclusive Coin thread on bitcointalk
https://bitcointalk.org/index.php?topic=1546005

Thanks to Transfer Coin,
and http://thecryptoworld.org/how-to-setup-your-masternode



if you feel like donating and excl, please use this address
EXCL : ER2Z8HqUKdpBDGbo4cgZfU9uvv2pAwVoxr

Thursday, 22 October 2015

managing the game wallet


it has just occurred to me the simple way to manage the game wallet.
(this is the bumba game where coins are regularly deposited into a publicly shared address)
every time the game address is updated, there is no need to keep that address, nor any wallet with that address.
the idea is, you have an address that you constantly send your coins to, and once you are in the game wallet you can send those coins there.
when the address is updated, delete the game wallet.dat and re-open with a fresh wallet. import the new privkey

however if you want to stake, then you will need to keep the wallet with your coins in it open.

REMEMBER all your coins are in these wallets. back them up and keep them safe.

...                                      
...                                      
simple version ...
one - generate a personal address
two - send coins to that personal address
three - create a new game wallet




          
making sure your wallet-qt is stopped.
go to your datadir and rename (or move) the current wallet.dat,
if there are no files called wallet.dat, the wallet-qt will create a brand new file on start up.

start up the wallet-qt, this will generate a brand new key pool which lives in the wallet.dat file,
get a new recieve address. copy this address somewhere handy so you can refer to it in a minute.
optionally dump the private key associated with this address for extra safe keeping.
          
stop the wallet-qt, go to your data directory.
the new wallet.dat is your new personal wallet. rename it to something obvious (eg wallet.datPERSONAL) and optionally back up externally.
     
rename the previously backed up wallet.dat and restart. this should now start with your previous transactions.
move all the coins to your new personal address.
          
shutdown the wallet-qt
rename (or delete) the now defunct wallet.dat
restart the wallet-qt (with another brand newly created wallet.dat file)
import the current game private key.

                              
                              
now whenever the game address is changed, you can now rename (or delete) the current game wallet.dat, create a new one, and import the new private key.
repeat everytime the address updates.


if you want to stake with this process.
whenever you create a brand new wallet, you can import both the game key AND your personal key, then your coins will be available to stake, and the game coins will show as well.

however you will need to use coincontrol to manage sending the game coins as otherwise you may just send your private coins.


                                       
                                       
                                       

note: when you boot off a wallet.dat backup. it can take a few minutes as it needs to scan the blockchain for address history.
an alternative option is to use a similar process of renaming with the entire data directory. you would duplicate the bumbacoin2 folder and then manipulate it's name and the internal wallet.dat.

the shortcomings of this process is an old backup of your data directory will need to sync the blockchain before it can be used.
also depending on the blockchain this folder can be a gigabyte or more each time.

i will dedicate a future post to this process.

Tuesday, 20 October 2015

Cleaning up your wallet-qt when it clogs with transactions.

how to clean yr wallet-qt


you data directory holds a complete copy of the block chain, and your wallet-qt holds every single transaction that has taken place for each address you "own".
these competition addresses have been subject to an awful lot of transactions :D

it can be useful to create a clean slate now and then. to much information can clog your wallet-qt.


the above wallet was becoming very sluggish.

things to know - all your private/public keys are stored in a file called "wallet.dat", this file is in your data directory.

to help manage your addresses, you can have multiple wallets with different addresses. this is done by having multiple wallet.dat files, then you can switch between them as you desire.



here is a picture of my macintosh data directory, in it you can see a wallet.dat and a wallet.datBAK. I swap wallets by renaming the files, it's also possible to keep wallet.dat's elsewhere and move them as you will.

to swap it's necessary to STOP your wallet-qt, before swapping.

DONT FORGET these files hold your access to all your coins. if you break them, you could lose all your coins. so keep backups of either the wallet.dat files, or the privkeys or both.

           

which leads back to HOW TO CLEAN YOUR WALLET. this is simply done transferring all desired coins to a new empty address.


TL/DR           
step 1. generate a new address
step 2. dump private key
step 3. send coins to new address
step 4. quit wallet
step 5. rename wallet.dat to wallet.bak (or whatever)
step 6. restart wallet
step 7. import private key from step 2

INDEPTH VERSION           


step 1. go to receive coins, press New Address button, the above dialog will popup, here you can name the address, then when you press ok it will display a new address.
copy this new address
eg B8QX8peKA9LvDb4Ya5GaMWwwLQoukV2aRY



step 2. go to Help/Debug window/console, type in:
> dumpprivkey B8QX8peKA9LvDb4Ya5GaMWwwLQoukV2aRY

 step 3. go to send coins, send them.
this shot is using Coin Control to help specify which coins. this is not strictly necessary in this scenario but it maybe useful.
to access Coin Control, go to Preferences/Display, tick "Display coin control".

step 4. quit wallet


step 5. rename wallet.dat -> wallet.bak
i am using wallet.datBAK02, you can use whatever you want

in this case there is no actual need to worry about the lack of wallet.dat file as the wallet will create one with new keys on startup.

step 6. restart wallet.


there will now be a new wallet.dat file in your data directory.


you will have no transaction data

step 7. go to debug console, type in:
>importprivkey Pe69Ten35qDWqc5cHbGEZfG5bq9npRtY8WkjXAvfGGaJiUQMFo63 newaddress 
it will hang for a moment. 
above i have named the imported key, that is not necessary, but it maybe useful for neatness.


then when it finishes your new wallet should have all the coins

--

OR 

send your coins to an external site, such as cyptobetfair.com or an exchange (when bumbacoin is on one)

step 1. go to an external site, and get a deposit address
step 2. dump private key
step 3. send coins to new address
step 4. quit wallet
step 5. rename wallet.dat to wallet.bak (or whatever)
step 6. restart wallet
step 7. import private key from step 2