Hi all, looking for some help with my Raspberry Pi nodes; they only run solarcoind daemon not SolarCoin-Qt, is therea way to load the bootstrap of the blockchain?
I tried unzipping bootstrap.zip into .solarcoin directory but that didnt work. I set the solarcoin.conf with server=1 and daemon=1 as well. I tried starting solarcoind -rescan and solarcoind -loadblock=/home/pi/.solarcoin/bootstrap/blk0001.dat
Any ideas? Im making a new Raspberry Pi node for a friend and syncing the block-chain takes days.
You might have better luck taking your question to the slack channel.
https://solarcoin-group.slack.com/x-33423960289-36618089767/
Thanks I had asked on Telegram and Slack a few months ago, I realised I had not checked in with this forum though so thought it was worth asking. If anyone wants to build a Raspberry Pi node, the instructions are on: https://github.com/Scalextrix/SolarCoin-Raspberry-Pi-Node |
|
|
|
|
Hi all, looking for some help with my Raspberry Pi nodes; they only run solarcoind daemon not SolarCoin-Qt, is therea way to load the bootstrap of the blockchain?
I tried unzipping bootstrap.zip into .solarcoin directory but that didnt work. I set the solarcoin.conf with server=1 and daemon=1 as well. I tried starting solarcoind -rescan and solarcoind -loadblock=/home/pi/.solarcoin/bootstrap/blk0001.dat
Any ideas? Im making a new Raspberry Pi node for a friend and syncing the block-chain takes days.
|
|
|
|
Just some more info on the Raspberry Pis, Im now using my Pi2 as my fulltime staking machine and have all of my SLR on it. So I hope shortly to be able to confirm a staked block. I have done a bunch of transactions without issues. My Pi seems more reliable at syncing with the block-chain than my windows machines  this is the best news. I have a Pi3b on chain as well. Now, it is about 50% solar powered, because we are in December here in Tokyo. But when I take it to the Emirates I will try to get it more solar powered. Even on the very worst of winter days here in Britain, my 4kWp rooftop system should produce enough to run my Pi2 No batteries so the night time will be on grid power. I can pretend my exported energy is shipped back to me! |
|
|
|
Pi2 staked a block |
|
|
|
Just some more info on the Raspberry Pis, Im now using my Pi2 as my fulltime staking machine and have all of my SLR on it. So I hope shortly to be able to confirm a staked block. I have done a bunch of transactions without issues. My Pi seems more reliable at syncing with the block-chain than my windows machines |
|
|
|
For those interested. A team active on Telegram has gotten solarcoin up and running raspberrypi which is very cool. https://en.wikipedia.org/wiki/Raspberry_Pi That means a solarcoin node for $35 that could be posting live solar production data and or earning interest while maintaining the chain with POST is quite cool. Obviously 1gb storage limitation is an issue so either enhanced storage or a version using checkpoints might be considered as solutions for full node. well done to the team of community members. We are waiting for a summary and write up from Luke and team here is what is up on steem: https://steemit.com/cryptocurrency/@jza/build-a-headless-solarcoin-node-on-raspberry-piUnfortunately the first Pi I got syncing had an SD card problem around 1,330,000 blocks synced. A couple of us have other Pis synced over the million block mark, so hopefully we will be testing transactions and staking in a few days. |
|
|
|
Installed the 2.1.7.1 last night and it seemed ok, so went to bed. Got up this morning and it wasn't syncing again, will try some more triage.
I will be home in a couple of hours to try starting over. Pretty sure we are going to have to revert back to before the hardfork though. Its pure chaos right now and everything used to work a week ago Its all OK now on my end, did a new blockchain reload and its been stable for some hours |
|
|
|
|
Installed the 2.1.7.1 last night and it seemed ok, so went to bed. Got up this morning and it wasnt syncing again, will try some more triage.
|
|
|
|
|
I seem to be back on the long chain again, so far so good
|
|
|
|
Thats exactly what I posted yesterday when I temporarily fixed my wallet. However I am still having issues so the problem must be elsewhere
I'm currently trying this again but it just fixes the problem for a few hours and then the wallet gets stuck again...
Did your solarcoin.conf have just the master-node? Yes I assume it did since I did a fresh Re-Install and didn't use a custom .conf file Give me five minutes. I'm rebuilding the bootstrap.zip now so it is as current as possible. Following the steps to the letter, just doin the wallet rescan now, confirmed the masternode in the conf file EDIT: All done, in sync for now.......... |
|
|
|
Alright, I seem to be back in business, I didnt do anything, it just synced while I wasnt looking, weird EDIT: false alarm, Im on a chain about 700 behind the block explorer, wondered why I was staking every few minutes  in wallet explorer has height 1455698, Im staking on 1454964 2nd EDIT: taken my wallet offline, no point in contributing to the bad chain |
|
|
|
|
My machine hibernated last night, now Im stuck unable to sync again, also the balance was wrong again!
I rescanned the blockchain and that fixed the balance but this is getting quite frustrating, it wont sync.
Am I getting banned or something, I have plenty of connections?
EDIT: OK I noticed in the console command getinfo that my IP was looking quite strange, a hexadecimal almost like an IPv6 address. I reset my WAN IP by jumping on a VPN, restarted the wallet and the IP now shows like an IPv4 address and I started syncing, it progressed a couple of hundred blocks and Im stuck again now.
|
|
|
|
All, We have just issued version 2.1.7, protocol version 70005, to fix the problem described below: "The reduced txn fee change caused 2.1.1 nodes to fork because 2.1.6 nodes were not paying enough fees. This in turn caused 2.1.6 nodes to fork sporadically." Please update your Qt wallet ASAP and begin staking so we can get the network moving again. Note: This update requires a Blockchain Reload. This is due to the fact that some 2.1.6 nodes are ahead of the master node, and we want to get everyone one the correct chain. After the reload, please rescan your wallet. If you are running a daemon, you can download the bootstrap.zip here: http://blockexplorer.solarcoin.org/downloads/bootstrap.zipPS: We will be notifying the exchanges and explorer ASAP. The website will be updated later today. PPS: After the rescan, you may see conflicted transactions from earned interest. You will make up the "lost" interest in future stakes. Hi Steve, Please let us know when the Explorer has been updated, so that we are sure we have the correct height there to compare to. Thanks! I got syncd and went ahead of the explorer by more than 10 blocks, also my balance went wrong again so re-scanning (again) |
|
|
|
All, We have just issued version 2.1.7, protocol version 70005, to fix the problem described below: "The reduced txn fee change caused 2.1.1 nodes to fork because 2.1.6 nodes were not paying enough fees. This in turn caused 2.1.6 nodes to fork sporadically." Please update your Qt wallet ASAP and begin staking so we can get the network moving again. Note: This update requires a Blockchain Reload. This is due to the fact that some 2.1.6 nodes are ahead of the master node, and we want to get everyone one the correct chain. After the reload, please rescan your wallet. If you are running a daemon, you can download the bootstrap.zip here: http://blockexplorer.solarcoin.org/downloads/bootstrap.zipPS: We will be notifying the exchanges and explorer ASAP. The website will be updated later today. PPS: After the rescan, you may see conflicted transactions from earned interest. You will make up the "lost" interest in future stakes. I cant get synced on the new version, I have connections but the blocks are just getting further behind did you reload the blockchain? Yes Sir I did, will try again this morning |
|
|
|
All, We have just issued version 2.1.7, protocol version 70005, to fix the problem described below: "The reduced txn fee change caused 2.1.1 nodes to fork because 2.1.6 nodes were not paying enough fees. This in turn caused 2.1.6 nodes to fork sporadically." Please update your Qt wallet ASAP and begin staking so we can get the network moving again. Note: This update requires a Blockchain Reload. This is due to the fact that some 2.1.6 nodes are ahead of the master node, and we want to get everyone one the correct chain. After the reload, please rescan your wallet. If you are running a daemon, you can download the bootstrap.zip here: http://blockexplorer.solarcoin.org/downloads/bootstrap.zipPS: We will be notifying the exchanges and explorer ASAP. The website will be updated later today. PPS: After the rescan, you may see conflicted transactions from earned interest. You will make up the "lost" interest in future stakes. I cant get synced on the new version, I have connections but the blocks are just getting further behind |
|
|
|
agreed, i have a theory that because there wasn't too many full nodes that many of them got onto the "wrong" chain, this caused stability problems for all main full nodes. Please correct me if I am off here. I was thinking through and the only way to improve this is to have more full nodes so the probability after each fork of this happening decreases. I realized yesterday after doing TXID certifications for our solar plant reports, that we were on the wrong fork (possibly for 2 days). So all of our wallets have been repaired now. The main way to fix it was to "reload blockchain". In general reliability for us is (1. Windows, 2. MAC, 3. Linux...) and I am not sure of the reasons for differences in reliability across platforms. Has anyone got a stable 2.1.6 Linux full node synced? I am very far behind on block count on ours. Looks like the wallet occasionally reports the wrong amount of coins available also. After a rescan it works itself out. We need some serious bugs fixes.
Hey, Im going to try and run a fullnode for the first time as I think I have a low power solution Im prepared to leave on 24/7, do I just have to add 'listen=1' to my config file? EDIT; What ports to forward? |
|
|
|
Looks like the wallet occasionally reports the wrong amount of coins available also. After a rescan it works itself out. We need some serious bugs fixes.
Yes, same here, its wildly off, I rescanned and reloaded the blockchain and it still cant add up, it seems to be when coins are staked the maths goes wrong. |
|
|
|
Hi all,
Does anyone know if i can use the same wallet.dat concurrently on two different computers ?
Reason : I have a running wallet staking on a remote site and i cannot switch it off remotely.
I 'd like to turn on the new wallet version on my actual computer.
I am wondering if i am going into trouble .
Thanks
This shouldn't be a problem. I would assume the following. But appreciate others to comment: 1. for transactions, it is unlikely you will be sending transactions simultaneously from both machines so ok. 2. for received transactions this is a read of the local chain as pulled down and resolved so shouldn't be an issue. 3. staking: If the same wallet stakes twice, it is attempting to find a block and then submit that "block solution" for the minting reward. It would make sense that the consensys algo would accept the initial solution submitted from a verified minting wallet and reject the subsequent submission. This would be important to prevent a sybil type of attack. 4. The one issue I don't know about is the impact on imputed calculated stake time. My assumption is that regardless of the machine submitting blocks, the stake time is calculated at the wallet level by lock-up. Having multiple wallets open begs the questions of control of staking. My assumption is that stake time/amount is relinquished reset the moment a wallet stops staking, if the follow block has a staking wallet the staking wallet would reset the "stake" toggle set. Given the treatment of staking time it seems the best thing to do would be have both wallets stake continuously. Please note these are assumptions. Steve Woods would have a better answer on the impacts of a stake state that toggled back and forth due to conflicting wallets. My guess is that the impacts to the minting reward are greater than 50% (1 machine on / 1 machine off) as the time calculation in POST has a non-linear function. I have my wallet on 2 machines and I have run them in parallel over short time periods, I didnt see any obvious problems. |
|
|
|
2.1.6 is now live. can get it by looking for updates in the wallet. or going to: www.solarcoin.orgI upgraded, all working fine |
|
|
|
|
Show Posts
