Sounds good all signed up and CPU is waiting to mine! Good luck with your CPU on X11.
|
|
|
Yes i use boostrap 20,7 Mb but it cant load it, debug log is empty
Bootstrap tested on Linux and Win and it works perfectly. It must be some other issue you have - maybe with the compile on your platform.
|
|
|
The port should be 14642.
Does this mean port 14642 must be opened on the firewall for staking?
|
|
|
Chill.
My gut feel is that coins that trade on the exchange are just tokens or placeholders. The real coins are in the wallets and their systems maintains a record of trades in the tokens that are transferred from real wallets when required eg. withdrawal from an exchange. A swop appears seamless to the end user and the exchange can therefore just refer to their systems for the balances at a certain point. When the new coin is activated they just link the token to a new real coin and the user then just generates a new address. As long as they do not allow withdrawal of old coins after the swop time all should be fine as the exact point of admin to effect the swop is then irrelevant. If users trade or not during/after a swop does not matter and they are just trading in "new" coins at this point without knowing it. When the update and admin happens (change in ticker name and linking of WOC/WOCX token from WOC to WOCX) they can let withdrawals happen again in new coins. This would allow things like an ICO or other trading activity before a wallet is released.
The above is just speculation but would make sense from a practicality and flexibility point of view.
|
|
|
Also got my first stake Presstab, thanks for your fantastic work! Agreed. Thanks presstab.
|
|
|
Fork seems live and staking seems to be working because blocks are moving although slowly.
|
|
|
The port should be 14642.
Is it necessary to add that in the Analcoin.conf?
|
|
|
This is normal i compile new wallet at beaglebone and have 0 connection ?
Did you get any errors? 1) Qt wallet or daemon? 2) If Qt was it Qt5 or Qt4? 3) Do you perhaps have a firewall on that is preventing connections? 4) Do you have output files of your qmake and make as well as your make makefile processes for further analysis? 5) Do you have an active working Internet connection on the device? 1) Qt wallet 2) Qt4 from our github 3) Probably not because i have work Tron wallet and all is good. 4) i havnt any output but i havnt any errors 5) Yes First of all, make sure you have all the details in the Analcoin.conf file as per the postings above. (Capital "A" in Unix) If that does not solve it, try rm -rf your directory where you did the build as well as the ~/.Analcoin directory (make a backup of your wallet first). Re-download the source. Do an apt-get update and apt-get upgrade. Also make sure you have all the dependencies installed - if you are unsure, install the list of dependencies in the Raspberry Pi installation script above. Then re-build, re-download the chain and put your wallet back. You can also try placing the bootstrap.dat above in your ./Analcoin directory to save some time as it should be compatible with your device. Can you send me text from Analcoin.conf ? rpcuser=user rpcpassword=password rpcallowip = 127.0.0.1 rpcport = 32119 port = 32118 server = 1 daemon = 1 listen = 1 addnode=37.187.245.222 addnode=94.156.230.246 addnode=95.145.103.84 addnode=98.213.214.114 addnode=45.55.134.166
|
|
|
This is normal i compile new wallet at beaglebone and have 0 connection ?
Did you get any errors? 1) Qt wallet or daemon? 2) If Qt was it Qt5 or Qt4? 3) Do you perhaps have a firewall on that is preventing connections? 4) Do you have output files of your qmake and make as well as your make makefile processes for further analysis? 5) Do you have an active working Internet connection on the device? 1) Qt wallet 2) Qt4 from our github 3) Probably not because i have work Tron wallet and all is good. 4) i havnt any output but i havnt any errors 5) Yes First of all, make sure you have all the details in the Analcoin.conf file as per the postings above. (Capital "A" in Unix) If that does not solve it, try rm -rf your directory where you did the build as well as the ~/.Analcoin directory (make a backup of your wallet first). Re-download the source. Do an apt-get update and apt-get upgrade. Also make sure you have all the dependencies installed - if you are unsure, install the list of dependencies in the Raspberry Pi installation script above. Then re-build, re-download the chain and put your wallet back. You can also try placing the bootstrap.dat above in your ./Analcoin directory to save some time as it should be compatible with your device.
|
|
|
This is normal i compile new wallet at beaglebone and have 0 connection ?
Did you get any errors? 1) Qt wallet or daemon? 2) If Qt was it Qt5 or Qt4? 3) Do you perhaps have a firewall on that is preventing connections? 4) Do you have output files of your qmake and make as well as your make makefile processes for further analysis? 5) Do you have an active working Internet connection on the device?
|
|
|
Awesome work! I am glad you were able to work it through Why 8gb? To leave some space for other stuff. One might be able to get away with a 4GB but it will be close. I had about 3GB free on a 8GB card after the testing. Ill do a test with a 4GB card as well to see what happens.
|
|
|
Here are the Raspberry Pi wallets based on the updated source - both the Qt and the headless daemon. Important: 1) The wallet was built on a Raspberry Pi2 (ARM7) running Raspbian. It might work on an older Pi but I have not tested it 2) Installation directory for binaries is ~/opt/analcoin 3) All that is needed is to execute the command below on your Pi in a terminal window and aftwards you click on the Analcoin icon on the desktop 4) An Internet connection is required for the installation 5) A bootstrap.dat is used to fast track the blockchain sync 6) You need at least an 8GB memory card 7) The installation itself takes about 30-45min and the loading of the blockchain (once-off) another 30-45min 8.)You cannot just download the binaries, you have to run the script to get the dependencies as well else it will not run Let me know about any issues that you may encounter. Command to execute to kickstart the installation: wget https://bitbucket.org/jc12345/analcoin/downloads/analcoin_installation_pi.sh && chmod +x analcoin_installation_pi.sh && ./analcoin_installation_pi.sh Link to installation script Link to Analcoin-Qt Link to Analcoind Link to bootstrap.dat Link to checksums
|
|
|
Hello all. Well first of all sorry for not being about today, I have some good news; 1 - It is my birthday today 2 - I am 40 today! OMG! 3 - I started a new job! 4 - Analcoin hard fork happens! So that's why I wanted the hard fork to happen today, rather than yesterday or the day before Hope everyone is ok with that. It will either be a good omen or a bad omen time will tell. So yes today is Butoshi Anamoto's birthday For Real!!!!!! Perhaps Buttoshi Anamoto is actually the Queen, her birthday is today also! Spooky - I have never seen them in the same room at the same time either! Looking forward to see what happens at 11.30pm tonight, fingers cross for a successful transfer across to the new fork. GOOD LUCK EVERYONE! Congratulations! I hope you have a wonderful day and prosperous year ahead.
|
|
|
Since I have been around the block a few times, I will let you guys know what I expect for this fork:
I expect there to be a general shortage of stakable blocks after the first tidal wave of stakes hit after the fork. The difficulty will probably raise because of all the blocks have a lot of weight. At a 60 second block time there are 1440 stakes per day, and it takes one day for them to be eligible to stake. This might not happen, but there is a good chance it does. It wouldnt be a bad idea to stake a few blocks, and then reserve the rest of your blocks for later in case the network runs low on stakable blocks. Locking your wallet is enough to stop staking.
Other than that, things should hopefully be smooth. Its possible that a few chains are created after the fork but I don't expect this to be a problem. I will come out with an updated wallet client in a day or two with the fork checkpointed.
It might be good for people to take lets say 1/3 of their coins and send them in 10-20 coin chunks around to a second address which can start maturing for tomorrow. The chain will be ticking over manually until later today. This should actually have been done yesterday. What do you think presstab?
|
|
|
Staking percentage doesn't look like 125%.
{ "Blocks" : 50350, "Current Block Size" : 1000, "Current Block Tx" : 0, "Difficulty" : { "Proof of Work" : 214758.34261646, "Proof of Stake" : 0.00024414, "Search Interval" : 1 }, "Block Value" : 300000000, "Net MH/s" : 0.00000000, "Net Stake Weight" : 81.19907187, "Errors" : "", "Pooled Tx" : 0, "Stake Weight" : { "Minimum" : 140314, "Maximum" : 0, "Combined" : 140314 }, "Stake Interest" : 3000000, "Testnet" : false }
ROFL Step 1: Read thread. Step 2: Run that again after 23:30 GMT tonight. If your answer is the same then as now then we can become concerned. if(nTime > FORK_TIME) nSubsidy = nCoinAge * COIN_YEAR_REWARD_2 / 365; static const int64_t COIN_YEAR_REWARD_2 = 125 * CENT; // fork to 125% annual interest static const unsigned int FORK_TIME = 1429659000; // forking on Tue, 21 Apr 2015 23:30:00 GMT
|
|
|
I have all the code ready and a compiled wallet. Just want the final go ahead to release a binary out in the wild. The fork is still scheduled for this Tuesday the 21st. If this is not enough time I can recompile with a later fork date (this is extremely easy to change). I added MultiSend, but we will need for staking to be functional after the fork before we can properly test the code. Find the repo at github.com/presstab/analcoin If this is the final code then I recommend someone fork my repo, as I am not going to promise to keep this repo up forever. Excellent. Have you added coin control as well to split/combine blocks?
|
|
|
nice added to cyptsy i think we cant call scam for atleast another 2 day so all you guys calling scam should be jumping in now buying up some cheap coin its not going much lower than this
Unless of course if they are right.
|
|
|
With the volume of the last day or so that ugly yellow bar at the top of Bittrex will probably disappear on Friday and hopefully never come back.
|
|
|
|