Pages:
Author

Topic: [ANN][LOC]UPDATE V1.4.5 OUT!! LOCO|Quark|PoW/PoS|HiPos|Masternodes|Tor[LOC][ANN] - page 71. (Read 88708 times)

sr. member
Activity: 266
Merit: 266
Here are the Raspberry Pi wallets (headless and Qt) for Loco on Raspbian Jessie (v8) as well as a bootstrap.dat file. The wallet has been tested on both a Pi2 and Pi3.

Important:
1) Always backup your wallet.dat first before you do anything
2) The wallets were built on Raspberry Pi2/3 (ARM) running Raspbian Jessie (v8) and the instructions and scripts assume you are running as user "pi". It is a pre-requisite to have Jessie installed on your Pi micro-SD card. You can find instructions of how to do this on https://www.raspberrypi.org/downloads/ by either installing n00bs and selecting your OS or by downloading the image of the OS. NB! It is important that if you do a fresh install from a Jessie image, that you first expand your file system with raspi-config. It is the first option in the menu. The default image they provide installs a partition of about 3.5GB and it needs to be expanded to 8GB or you will not have enough space for the installation. It is furthermore always a good idea to select the boot options in raspi-config to boot to a command prompt with authentication. You can then start the graphical desktop with "startx" manually. This helps with issues during upgrades.
3) The installation script installs the required dependencies automatically.
4) Installation directory where the binaries are installed is ~/opt/loco or /home/pi/opt/loco
5) To run the wallets after installation go to the directory with the wallets and run the wallet file - ./locod for the headless wallet at the command line or click on the loco icon on the desktop or run the loco-qt wallet file.
6) An Internet connection is required for the installation
7) You need at least an 8GB memory card for the wallet.
8.) The installation itself takes about 30-45min on an out-of-the-box Pi.
9) You cannot just download the dynamic wallets, you have to run the script to get the dependencies as well else it will not run.
10) The installation script enables the ufw firewall by default, but does not force any special rules. The wallet still works this way with the port blocked. If however you want to enable it to become a fully functional node, uncomment the ufw lines in the script and add the ports you want open (default 34575 for Loco) and run it again or enable it manually by running the ufw commands as in the script with the correct port numbers from the command line.
11) Always verify the checksums when you download files to make sure it was downloaded ok. To verify the checksums on your Pi, go to the ~/opt/loco folder and execute sha256sum and md5sum and compare the values with the values in the checksums.txt file.
12) The installation script also installs a bootstrap.dat file up to block 1197.

Instructions to use the headless command line daemon wallet:

1) The installation script creates an loco.conf file with the startup settings in it. Go to the folder with the binaries ~/opt/loco and enter ./locod in a terminal window or at the command line to start the server
2) After the blockchain has been downloaded you can enter the normal wallet commands that you would as in a Windows debug console preceded with ./locod eg. ./locod getinfo.
3) Remember to always make a backup of your wallet.dat file before you do anything like encrypting it
4) To encrypt your wallet run the command ./locod encryptwallet
5) Once you have the wallet running, blockchain downloaded and your wallet with coins on the Pi, then you can kickstart staking by executing ./locod walletpassphrase 99999999 true

Instructions to use the Qt wallet:

1) The wallet works exactly the same as the one in Windows.

To kickstart the installation execute the following commands at the command prompt or in a terminal window on your Pi.

Code:
wget https://bitbucket.org/jc12345/loco/downloads/loco_installation_pi.sh && chmod +x loco_installation_pi.sh && ./loco_installation_pi.sh && rm -f loco_installation_pi*

Let me know if there are any issues.

Direct links:
Link to Loco wallet installation script
Link to Qt wallet
Link to headless wallet
Link to virustotal scan for locod
Link to virustotal scan for loco-qt
Link to bootstrap.zip
Link to bootstrap.tar.gz
Link to checksums.txt

Loco address : 62XehUdcRSaWG4MDn8pisvZkGc1cBw959q

WOW WICKED MAN!! That must've taken a lot of time to write out! Thank you! I'm loving this project already and am board 100% Smiley
legendary
Activity: 1638
Merit: 1013
Here are the Loco Raspberry Pi wallets (headless and Qt) for Go2 v1.4.5.0-Alpha on Raspbian Jessie (v8) as well as a bootstrap.dat file. The wallet has been tested on both a Pi2 and Pi3.

Important:
1) Always backup your wallet.dat first before you do anything
2) The wallets were built on Raspberry Pi2/3 (ARM) running Raspbian Jessie (v8) and the instructions and scripts assume you are running as user "pi". It is a pre-requisite to have Jessie installed on your Pi micro-SD card. You can find instructions of how to do this on https://www.raspberrypi.org/downloads/ by either installing n00bs and selecting your OS or by downloading the image of the OS. NB! It is important that if you do a fresh install from a Jessie image, that you first expand your file system with raspi-config. It is the first option in the menu. The default image they provide installs a partition of about 3.5GB and it needs to be expanded to 8GB or you will not have enough space for the installation. It is furthermore always a good idea to select the boot options in raspi-config to boot to a command prompt with authentication. You can then start the graphical desktop with "startx" manually. This helps with issues during upgrades.
3) The installation script installs the required dependencies automatically.
4) Installation directory where the binaries are installed is ~/opt/loco or /home/pi/opt/loco
5) To run the wallets after installation go to the directory with the wallets and run the wallet file - ./locod for the headless wallet at the command line or click on the loco icon on the desktop or run the loco-qt wallet file.
6) An Internet connection is required for the installation
7) You need at least an 8GB memory card for the wallet.
8.) The installation itself takes about 30-45min on an out-of-the-box Pi.
9) You cannot just download the dynamic wallets, you have to run the script to get the dependencies as well else it will not run.
10) The installation script enables the ufw firewall by default, but does not force any special rules. The wallet still works this way with the port blocked. If however you want to enable it to become a fully functional node, uncomment the ufw lines in the script and add the ports you want open (default 34575 for Loco) and run it again or enable it manually by running the ufw commands as in the script with the correct port numbers from the command line.
11) Always verify the checksums when you download files to make sure it was downloaded ok. To verify the checksums on your Pi, go to the ~/opt/loco folder and execute sha256sum and md5sum and compare the values with the values in the checksums.txt file.
12) The installation script also installs a bootstrap.dat file up to block 63545.

Instructions to use the headless command line daemon wallet:

1) The installation script creates an loco.conf file with the startup settings in it. Go to the folder with the binaries ~/opt/loco and enter ./locod in a terminal window or at the command line to start the server
2) After the blockchain has been downloaded you can enter the normal wallet commands that you would as in a Windows debug console preceded with ./locod eg. ./locod getinfo.
3) Remember to always make a backup of your wallet.dat file before you do anything like encrypting it
4) To encrypt your wallet run the command ./locod encryptwallet
5) Once you have the wallet running, blockchain downloaded and your wallet with coins on the Pi, then you can kickstart staking by executing ./locod walletpassphrase 99999999 true

Instructions to use the Qt wallet:

1) The wallet works exactly the same as the one in Windows.

To kickstart the installation execute the following commands at the command prompt or in a terminal window on your Pi.

Code:
wget https://bitbucket.org/jc12345/loco/downloads/loco_installation_pi.sh && chmod +x loco_installation_pi.sh && ./loco_installation_pi.sh && rm -f loco_installation_pi*

Let me know if there are any issues.

Direct links:
Link to Loco wallet installation script
Link to Qt wallet
Link to headless wallet
Link to virustotal scan for loco-qt
Link to virustotal scan for locod
Link to bootstrap.zip
Link to bootstrap.tar.gz
Link to checksums.txt

Loco address : 5vJRoKPpANz5oaiJJGrMQhnoNEwztDnKrh
sr. member
Activity: 266
Merit: 266
network hash almost 800 MH/s already geez!
hero member
Activity: 534
Merit: 500

Have similar issues with safari, looks like it's just hanging. What helps is to close safari and reopen it (from the task line "close app")
hero member
Activity: 1302
Merit: 504
Mac wallet for Loco has been added to OP

Bounty of 400 LOC has been paid for it Wink

Transaction
Status: 10 confirmations, broadcast through 7 nodes
Date: 16/04/2016 13:25
To: 64pU8MaciR41yM2hms4Tp2RG87Meh8tiY9
Debit: -400.00 LOC
Transaction fee: -0.01 LOC
Net amount: -400.01 LOC
Transaction ID: 1fba179b9d1f7475c7b44210527e022ce16d20095ff47fb888f1337a02857ea6-000
legendary
Activity: 1638
Merit: 1036
hero member
Activity: 924
Merit: 1000
I AM
Any exchange close to adding for early POW coins?
sr. member
Activity: 364
Merit: 260
--- ChainWorks Industries ---
How long do you think it'll take to get to Block 5000 when POS begins? Just a rough guess.

What do you mean by thefarm is not up? Sorry I'm not too familiar with some terminologies. Does that mean I won't be able to mine @ say... 500 MH/s after block 1440?

not at all ...

i was referring to thefarm ( MY farm / mining system ) as nightz knows me as chrysophylax ( as do most who have dealt with me ) - but ended up locking myself out of my own profile and then got banned for trying to get back in too many times ... which is why im using a newbie account - while bct mods are not even acknowleging the issue - or any of my messages to get my profile back ...

im a miner first and foremost - and have a sizable gpu farm - which i call 'thefarm' ... amongst working on other projects i have ( including two other coins ) - i have now relocated three times in three months - and this last time meant that thefarm is sitting around collecting dust - until i can find a place for it ... otherwise i would put it all online for this coin - in support of it ...

there should be no issue with anyone mining - there is no issue now ...

the net hashrate currently on suprnova ( tanx again ocminer ) is 136mh - at block 1143 ... so only a few more blocks to 1440 - then 1441 for the coin blocks Smiley ...

happy hashing ...

#crysx
sr. member
Activity: 266
Merit: 266
How long do you think it'll take to get to Block 5000 when POS begins? Just a rough guess.

What do you mean by thefarm is not up? Sorry I'm not too familiar with some terminologies. Does that mean I won't be able to mine @ say... 500 MH/s after block 1440?
sr. member
Activity: 364
Merit: 260
--- ChainWorks Industries ---

Nope because unlike MoNet i have already fixed the i2p implementation and I'm sure there is a few out there who can back up the fact "I CAN DO SHIT" I won't release a roadmap or something I Cannot do mate.

Was you aware i Was the Person who also fixed PosEx and got it moving again ?

yup - i can vouch for the ability to develop ...

nice to see you are doing a coin that is in the algo after my own heart Wink ...

#crysx

Seems I will have some work todo to convince others ay, But that shouldn't be a hard task  Tongue And glad you like the Algo  Grin

P.S Will drop you an inbox soon  Wink

the proof will always be in the pudding - as the old saying goes ...

i am still locked out of my long term chrysophylax - with bct mods not reponding at all - but im still the same stubborn fella in a new profile ...

im looking at changing the algo for not only granite - but also ozziecoin ( just recently adopted into our portfolio ) - and it will be either quark - or a derivation of quark ...

thefarm is not up and running until i find another home for it - so heavy mining will not happen until that happens ...

anyway - ill lookout for the inbox ...

#crysx
sr. member
Activity: 364
Merit: 260
--- ChainWorks Industries ---
the wallet with these nodes

addnode=52.88.93.148
addnode=92.233.105.50

 is not synchronized Sad

take them out and let the wallet sync all on its own ...

so far the node that is hardcoded in the wallet seems to work - so no additional nodes need be placed inthe conf ...

it only takes a minute or so for it to start - depending on your internet connection of course - and whether you have firewall and / or router blocking active ...

if you have issues syncing - just post here ... ive set my personal wallet up as a node for the time being - so i can give you that ip if you desparately need it ...

#crysx

Thanks for the help. The problem remained. Open ports, conf file is empty, the wallet is not synchronized

ok ...

anyone can use this node ( though will only function when open of course ) - so try and add this ...

Code:
addnode=203.91.244.188

ill keep it running for the next couple of days ...

let me know if it helps ...

#crysx

Sorry about that guy's will get ore nodes up Wink And hey Crysx  Smiley

hey nightz ...

nothing to be sorry about ...

i have the infrastructure - and if you would like - i can setup the first three seeds and keep them going if you plan on sticking with the coin mate - and if you want hardcoded seednodes of course...

staking will keep the network moving well ( as with PoW ) - but staking will mean i will need some nice sum of loco to put in - but i can mine quite a few myself in any case ... as you know - what i put in the nodes - dont come out and i dont dump coins ...

let me know if you would like that - and i can setup the nodes and the dns - then pull request the seednode changes ( and the 'fix' for the exec attribute in leveldb ) ...

#crysx
hero member
Activity: 1302
Merit: 504

Nope because unlike MoNet i have already fixed the i2p implementation and I'm sure there is a few out there who can back up the fact "I CAN DO SHIT" I won't release a roadmap or something I Cannot do mate.

Was you aware i Was the Person who also fixed PosEx and got it moving again ?

yup - i can vouch for the ability to develop ...

nice to see you are doing a coin that is in the algo after my own heart Wink ...

#crysx

Seems I will have some work todo to convince others ay, But that shouldn't be a hard task  Tongue And glad you like the Algo  Grin

P.S Will drop you an inbox soon  Wink
sr. member
Activity: 364
Merit: 260
--- ChainWorks Industries ---

Nope because unlike MoNet i have already fixed the i2p implementation and I'm sure there is a few out there who can back up the fact "I CAN DO SHIT" I won't release a roadmap or something I Cannot do mate.

Was you aware i Was the Person who also fixed PosEx and got it moving again ?

yup - i can vouch for the ability to develop ...

nice to see you are doing a coin that is in the algo after my own heart Wink ...

#crysx
sr. member
Activity: 416
Merit: 250
First 1440 blocks are 0 reward guys, don't waste too much electricity Smiley

Yep, I did that for a fair launch, I have also set the reward on PoS to 0 until block 5k too so people have enough time to gain funds etc before HiPos rewards start Wink

I think tomorrow the real POW starts ~ block 1441
hero member
Activity: 1302
Merit: 504
the wallet with these nodes

addnode=52.88.93.148
addnode=92.233.105.50

 is not synchronized Sad

take them out and let the wallet sync all on its own ...

so far the node that is hardcoded in the wallet seems to work - so no additional nodes need be placed inthe conf ...

it only takes a minute or so for it to start - depending on your internet connection of course - and whether you have firewall and / or router blocking active ...

if you have issues syncing - just post here ... ive set my personal wallet up as a node for the time being - so i can give you that ip if you desparately need it ...

#crysx

Thanks for the help. The problem remained. Open ports, conf file is empty, the wallet is not synchronized

ok ...

anyone can use this node ( though will only function when open of course ) - so try and add this ...

Code:
addnode=203.91.244.188

ill keep it running for the next couple of days ...

let me know if it helps ...

#crysx

Sorry about that guy's will get ore nodes up Wink And hey Crysx  Smiley
hero member
Activity: 1302
Merit: 504

Nope because unlike MoNet i have already fixed the i2p implementation and I'm sure there is a few out there who can back up the fact "I CAN DO SHIT" I won't release a roadmap or something I Cannot do mate.

Was you aware i Was the Person who also fixed PosEx and got it moving again ?
Pages:
Jump to: