start from scratch fixed it. everything is back in my wallet and V1.2 is working fine. Great to hear, thanks.
|
|
|
hi bosian,
yes it syncs when I use the old wallet.
just made a backup of everything an now i'm redownloading the blockchain. let's see what's happening.
OK thanks.
|
|
|
man, my sincere apologies, the download links are fixed now, i was too tired yesterday, did not verify the links. The links are there, but the url tag was wrong. Windows Client Downloads Mega.co.nz: https://mega.co.nz/#!Z59xXQaD!BE4IXkhNir5JmHzCYkGSSjyfO_AHCfxqc7UjQDpRihMSkydrive: https://skydrive.live.com/redir?resid=248417D5E47DC8A8!110&authkey=!AJEmTpszWW8hgYY&ithint=file%2c.zipSource Code Download https://github.com/grain-crypto/grainTo upgrade, if you use windows, just download the new client, unzip, and run it, nothing need to be changed. It will sync with your existing wallet. Just One short question. Downloaded the new version, tried to start the wallet and get an error "error loading blkindex.dat" Any suggestions? Thx in advance. Is your wallet in sync when you use the old client?
|
|
|
Upgraded to Grain 1.2. Is it normal that coins go from Balance to Stake?
That means you generated PoS blocks, which will put some coins in stake and after certain time of maturity the coins + interests will be returned to balance.
|
|
|
man, my sincere apologies, the download links are fixed now, i was too tired yesterday, did not verify the links. The links are there, but the url tag was wrong. Windows Client Downloads Mega.co.nz: https://mega.co.nz/#!Z59xXQaD!BE4IXkhNir5JmHzCYkGSSjyfO_AHCfxqc7UjQDpRihMSkydrive: https://skydrive.live.com/redir?resid=248417D5E47DC8A8!110&authkey=!AJEmTpszWW8hgYY&ithint=file%2c.zipSource Code Download https://github.com/grain-crypto/grainTo upgrade, if you use windows, just download the new client, unzip, and run it, nothing need to be changed. It will sync with your existing wallet.
|
|
|
Version 1.2 Released. Version 1.2 is not a mandatory upgrade, but you better upgrade it to make the whole network more secure. Version 1.2 has the latest checkpoints. Download links and source in github are both updated.
|
|
|
Thanks for your friendly reply. Yes, the issue (or rather: paradigm) you mentioned is clear to me - and I value anonymity and the de-centralized approach. But there are a few points that I would like to say about that: 1. Such update feature / notification feature should NEVER be mandatory, only optional for the type of User I mentioned who will gladly give up part of anonymity for convencience / peace of mind 2. The network itself will remain de-centralized. Most coins already have a centralized approach when it comes to software-distribution, though: GitHub or their homepage. So an autoupdate-feature would not change that 3. if the wallet actually only transfers the eMail-address + the QT version (and not addresses etc.), the anonymity is not much less than in e.g. this forum. Many people use their real names (I do, for example), many post their addresses, some use their regular eMail addresses etc. I am almost sure that if somebody would do a big datamining trying to find personal information on a given user account (whose coin address is known because he used e.g. a giveaway thread), he would most likely succeed. So in theory, Cryptocoins can be anonymous, but in real life they are rather pseudonomous. And even that is weakened by every piece of information users leave of themselves in the www. So such notification feature doesn't really change much here - as long as (1) remains valid. Thanks again Yes I agree with you. There is a channel in the code, and Litecoin used it to broadcast messages for the mandatory upgrade. I still have reserve to attach email. I think anonymity without any personal info such as email is important. Yes some people don't care, but a lot do. To broadcast a newer version or make the client display certain messages if the code is too old are both good ways and are currently implemented (for example, if the checkpoints are 90 days behind, the client will display "Checkpoints too old please contact developer for a newer version" or something like that.
|
|
|
Anyone have idea what does "Stake" in Wallet mean? There is around 60K show at balance of my wallet What should I deal with these "Stake"? This is the PoS block generation. Don't worry, it's like PoW mining, will return to your balance after certain time of "maturity", your balance will be added with some "interests". Noted and thank you very much for your quick respond You are welcome
|
|
|
Anyone have idea what does "Stake" in Wallet mean? There is around 60K show at balance of my wallet What should I deal with these "Stake"? This is the PoS block generation. Don't worry, it's like PoW mining, will return to your balance after certain time of "maturity", your balance will be added with some "interests".
|
|
|
Hi, Since not all users of this coin are as active as you are, may I ask for a feature in a future wallet version? Please implement one of the following features: 1) an autoupdate feature which automatically keeps the QT updated without the user doing anything (or with the user just clicking an "update" button which only appears when new updates are available - but where the entire update process is done automatically) 2) a notification feature where the user can enter his eMail address into the wallet and the wallet sends him an eMail when a new version is available? That requires - of course - that the wallet has a way to check for updates. But since Microsoft/Apple/Adobe/andalltheothers can do it, so can you :-) 3) (for those who don't even run their QT all the time) a notification feature where the user can enter his eMail address into the wallet and the wallet sends that eMail address plus its own version information to a central server of yours which then sends out an eMail when a new software version is available. And which sends a warning eMail when a mantatory update has to be performed. Naturally, as of today, the Cryptocurrency-community has been very active but with the price explosion of the Bitcoin last month, more and more "normal users" will enter the market. They will not keep their wallet running all the time. They will not check the forum all the time. But they might spend hard cash on buying this coin at an exchange and then send it over to their wallet. As a community, we even need that kind of passive user - and we need their money buying this coin. And when they find ways to spend or donate the coin, they will. And for that purpose they will open their wallets - but not in between. Having said this, I personally prefer feature (3) because it has a few advantage over the other 2: - It keeps even those "passive" users in the loop that do not run their wallet regularily.
- That way, if a really important change has to be made (e.g. a new blockchain), even those users won't lose their money because they get a notification. Think of the bad publicity when "normal users" start losing their money because they simply ignored their wallets for months only to find them not working anymore because weeks before, a new blockchain or equally invasive measure was introduced without them knowing.
- That feature can be extended for marketing purposes: add a checkmark "the makers of this coin are allowed to send me exciting news about this coin yaddayaddaya" - and voila you get yourself a free marketing database with tons of eMail addresses that you can use to keep engaging your users. Notify them of new shops where they can pay with this currency. Notify them of faucets. Notify them of exchanges that trade this coin. Notify them of the rise in value of that coin. And so on. Just keep engaging even the passive users - because to make a currency successful, you need every hand and every dollar you can get.
You guys and all the other professionals or those that have privacy concerns won't use that feature - and should never be required to do so. But the regular passive user will get that fuzzy feeling that he will be informed of important stuff without him spending much time checking bitcointalk or their wallets. And that will give him extra confidence when it comes to him spending the coin or buying the coin with his FIAT. Just a few additional remarks: - Naturally, the best possible combination would be (3) with (1) where the users gets a "move your ass and update your wallet or else..." eMail (friendly version, of course) - and then he opens the wallet and clicks on the "update" button and that's it for him.
- May be the required serverside portion (the thing that collects all version information and the eMail addresses and which also allows for sending out mass eMails to all users in that database) could be written in a generic way so that other virtual currencies can implement that feature, too?
- May be, future wallets should have a default setting that causes them to run in the background as a service whenever the computer starts. That way, even many passive users will contribute to the P2P network without them even knowing. But that was just a sideline remark and describes a completely different feature request. But then again, while you are at it... :-)
Don't know. What do you guys think about that feature request? Does anyone second that request? Does anyone have a better idea how to solve the above mentioned challenges that this new species of regular, passive users will introduce in the weeks and months to come? Thanks Matt GRA: 96cLQrQu9kYYMCn1cHEMsaiUDDuC9vnF8PP.S. Just a full disclosure: I have posted this same feature request to the thread of some other cryptocurrencies as well. Thanks for your great suggestions. But the key features of the crypto coins are (a) anonymous (b) de-centralized with email associated with wallet you violate (a) and in order for updates you need a centralized place to announce the new version. So I am not sure on these... We will read in more detail your suggestions, since it is pretty long and detail. Thanks again for your great suggestions, and I sent some tips to you.
|
|
|
Jolly Burner
I have some unconfirmed transactions from 26 th as well. I am having my first coffee for the day so once it kicks in I will have a closer look and let you know times etc.
unconfirmed PoS or normal transaction? PoS block generation can cause some orphans, this is normal, all the PoW/PoS coins do it. You can ignore them. New PoS blocks will be generated.
|
|
|
First day on pool without problem and actions manually. ~10000000 graincoin generated after restart Nice... some people reported unconfirmed transactions, the issue resolved?
|
|
|
By the way, we should really try and contact CoinedUp ( https://coinedup.com/Contact) about adding Grain. They seem way more interested in adding new coins than Cryptsy at the moment to grow their user base. They've added Lotto, Earth, and Billioncoin within the last couple of weeks and more coins means more traffic for all of us. The site is still a bit ugly but it's been rock solid for me; trades go through in a few seconds and withdraws are processed immediately. Yes this is a good exchange. I emailed them too...
|
|
|
The following list of people, please send me your wallet address, or post in this thread, to claim your supporter's bounty! Beeker dorcorax DRKMSTR Galimore luckygenough56 Mark77 Nolo paladin281978 theironman tx42 udjin123
|
|
|
One thing, has anyone else noticed that the debug.log file is growing very large? As of this morning it was over 110MB so I stopped my wallet, renamed it to start a new one, and restarted my wallet.
What it is showing are lots of these.
trying connection 184.78.158.84:11054 lastseen=9.0hrs getblocks 37083 to 00000000000000000000 limit 500 getblocks stopping at limit 37582 000000001f656535fd6f received getdata (3 invsz) getblocks 37083 to 00000000000000000000 limit 500 getblocks stopping at limit 37582 000000001f656535fd6f getblocks 37583 to 00000000000000000000 limit 500 getblocks stopping at limit 38082 73c9a23843e09cdc019e getblocks 37583 to 00000000000000000000 limit 500 getblocks stopping at limit 38082 73c9a23843e09cdc019e getblocks 37583 to 00000000000000000000 limit 500 getblocks stopping at limit 38082 73c9a23843e09cdc019e
etc, etc - it seems to be going through each peer and checking what block it is up to - and does this every time it receives a new block. Currently it is 1MB and has been running only 40 minutes or so.
Don't worry about debug.log, it's mostly useless. If it bothers you, you can stop qt-client, delete debug.log, and start qt-cleitn again. Everything will be fine.
|
|
|
My 1e6 coin showed up on the updated blockchain.
Hurray! Good job in making this a smooth fix devs!!!
[edit]
Before I celebrate too much, can someone verify that I have the correct chain?
15:32:56 <> getblockcount
15:32:56 <> 47115
tx42, you are on the supporter bounty list, please post you wallet address or PM me. Thanks.
|
|
|
tried in solo, i still get rejected blocks
What is your current block number? We should be at block 47268 now.
|
|
|
I think we started over from where the coin began generating only PoS blocks, so your tx probably was during this period and isn't counted, I think this may have been overlooked since most people aren't trading grain.
If the devs fork out transactions that were once legitimately on the blockchain, then most people will never trade grain. This really wouldn't be acceptable. tx42, a fork is done because the PoW is jammed. This is a typical process to fix the issue. Other coins did the same thing for fixing similar problems.
|
|
|
Hey Bosian,
I am using following nodes for solo mining. Is it true or do i need to add more nodes?
addnode=66.187.67.233 addnode=199.58.167.85 addnode=98.207.109.245
And last question, is the node sequence important? I mean writing the node on first line is changing something?
No, as long as you sync'd to the right chain, the addnode is not important anymore. The order doesn't matter. All info should be in your peer.dat, so even you remove addnode in your conf file, you should be OK now.
|
|
|
Also, following people please send me your wallet address or post it in this thread, you are eligible for the supporter's bounty, I added a few more people there. Those on the old list but not here should already have received the bounty, if you did not, PM me. Amph Beeker damnation dorcorax DRKMSTR Galimore Illusmare karky luckygenough56 Mark77 Nolo paladin281978 theironman tx udjin123
|
|
|
|