so I just downloaded the 1.5.2 wallet, but not syncing with the network. I wanna move my funds from cryptsy to my wallet. Can someone help me?
Please try version 1.999 https://github.com/Tranz5/bottlecaps/releasesLook for final release 2.0 here soon. |
|
|
|
Looks good Tyke! And good information from the guys. Nothing else I see need updated.  |
|
|
|
Difficulty has risen from 8 to 17 within the last 12 hours or so, while the price has been slightly declining. Litecoin hashing power has not changed during the same time, so no influx of ASICs.
This is not normal.
Any thoughts about this?
Is it more likely some kind of attack or is it an individual with lots of hashing power, who wants to earn Hobonickels via Mining instead of buying?
Hmm good observation. PoW attacks are probably hard to accomplish on HBN. First of all PoS/PoW hybrid adds an extra layer of security. Also the PoW diff adjusts every block, so it isn't going to be as easy for someone to come hash out a lot of blocks quick. Hard to know why such a quick and large rise in hash rate. No attack(that I can see), just someone or pool with large hash rate coming on board. Difficulty is adjusting prefectly to keep the 30sec PoW/PoS in line. They got a few quick ones at the beginning but not more then a few hundred hbn, before the diff adjusted correctly. |
|
|
|
Thought I would share my validation results for the new client (badass work btw Tranz!). The following was performed on Ubuntu 12.04 64 bit. QT and daemon source compiled without issue. Confirmed that the new client appears to generate stake blocks correctly. (Had older coins available that were stakeworthy.) Status: 4363 confirmations Credit: 0.039441 CAP Net amount: +0.039441 CAP Transaction ID: a40bbf7671c8ff14f8ab0d9fd94b2503e4caebd0de7c2a8669bc0a41726a32d4 Confirmed solo mining to the wallet is also functional (verified internal CPU, and RPC/GPU mining). Status: 3897 confirmations Date: 30 May 2014 17:50 Source: Generated Credit: 10.00 CAP Net amount: +10.00 CAP Transaction ID: a5a018de920af7a4096c35d19585ed55f8dc55602c7fd700c23ceb6d94072d92 Confirmed that the beta wallet is backwards compatible with the original wallet (ftm). Confirmed coins could be sent/received. Confirmed wallet.dat could be opened from both clients (not simultaneously), performed multiple times with no issues. Confirmed all coins mined on the new wallet were available from the old wallet and vice-versa. Confirmed stability, ran 72+ hours. No memory leaks, no thread locking. Also performed some cursory validation on the new coin control features, and new functionality in the debug console. And no issues to report! It's all looking REALLY REALLY good! Incredible functionality for a "beta". Thanks!. I am still looking for confirmation about a PoS. I have testnet running now. So hopefully that will answer my questions. |
|
|
|
What id the min stake age on 1.999? What is the intended min stake age for final version? I bought my first Bottlecaps yesterday, so I won't have be able to help you, sorry  Also, Tranz: could you check I have everything alright here for CAP (and HBN, while you're at it): Proof-of-stake List1.999 is the same as before 30/90 days. 2.0 will move it to 15/45 Both look good on your sheet. |
|
|
|
Any source code for the change?
Not a very good one from the looks of things. i requested a a pull request to made to the original repo so we can see whats been changed and as expected nothing. Great way to get other's opinion on source code changes zack... sorry but you messed with the original ADT v2 that you posted on github and were willing to make changes even if I didn't agree with them so I got it uploaded to my github account instead So what is that link please. I don't see any of the changes you mention in the source file from your links.. |
|
|
|
Please be aware. There may still be a change or 2 before we are completely done. So be sure to check back. Thanks. Should I avoid having my newly-acquired Bottlecaps on this wallet (I have a backup) and instead send them back to cryptsy? Should be safe I am running with it no problems, just make sure you get the final version once it is out, or you will have to redownlaod the block chain. As always make sure you have a good offline backup of your wallet.dat.. |
|
|
|
Tranz, I take issue with a section of code for the negative target patch. Specifically, it is this one: if (nActualSpacing < 0)
nActualSpacing = nTargetSpacing;
The difficulty should still increase if the time between blocks is less than zero, but this line of code makes it so that the difficulty remains static. If this issue is going to be fixed, I feel the more desirable option is below: if (nActualSpacing < 0)
nActualSpacing = 0;
I'm not a fan of the way Peercoin forks adjust difficulty because of attack vectors, and hopefully some hashrate and staking will increase the security of this chain. That is a discussion for another topic at another time, however. Please share your thoughts on my small suggestion Hi Math. Good suggestion and thanks for it. My thoughts on it are such that if you set the spacing to zero, and allow the difficulty to move up, as you suggested, you also allow the peer to rapidly increase the difficulty, which could result in a slow or even stuck block chain. I will keep this in mind, as I am still adjusting the hard fork. My uses of GetAdjustedTime will not work, so I am changing some functions to fit. Thanks for the feedback! |
|
|
|
|
Any source code for the change?
|
|
|
|
Don't mind guys, just pick up some nice cheap coins, let em stake and be happy in the future... wish i had more btc to invest.. hbn is one of my absolut favourite Coins! I'm in the same boat. I want more BTC to invest. My issue is constant checking of my progress. I convert HBN to BTC and see a huge loss but have to force myself to not jump ship. Sometimes it takes a bit of capitulation before the market makes a new surge forward. Buying right before a crash or selling right before a rally can take a toll on ones psyche. Make a trading plan and stick with it. Sell 50% of your interest and start to recoup your initial investment. While still holding the base and continuing to accumulate more! |
|
|
|
We were planning on an upgrade release before hardfork, correct? Flound, yes. I have at least 1 more commit to do. I am going to send you a PM here shortly. |
|
|
|
John Eden did not handed access over to Tranzz? Pity. That's why for monero we deliberately created the ANN with a dedicated, shared account. When you lose interest in a program, your last duty to it is to hand it off to a competent successor. Tranzz, how can I compile from source by cloning (not by wgetting the tar.gz)? There is no .git file? I'd like to just use pull to get the latest version. Thank you. Flound has access to OP. git clone git://github.com/Tranz5/bottlecaps Please be aware. There may still be a change or 2 before we are completely done. So be sure to check back. |
|
|
|
is there a website that can show me the total network hashrate for caps? preferably with a breakdown on pools.
please advise, thanks.
I'm not sure, but the net mh/sec is included in v 1.999-beta and soon to be released 2.0. under getmininginfo or clicking the thumbs up icon. |
|
|
|
The blockchain takes days to catch up. It's a bit of a problem for a pos coin.
The only computer I had take days was the Pi. A modern fast computer takes about 5-7 hours. A slower machine can at 12+. If it seems like the chain is stalled while downloading, sometimes 1 restart of the gui can help. |
|
|
|
I've been using the 1.999 beta wallet since it was released and I must say it looks very promising. I haven't had any trouble connecting to the network. I also tried to solo mine for a couple of hours and I got the impression it worked fine. Didn't had any luck finding blocks though.
But there's was one odd thing. I was sending some coins in quite rapid succession, like every 10 seconds or so, and sometimes the sent coins appeared as unconfirmed (sent without any confirmations yet) and moved from unconfirmed to my balance for as long as they didn't have any confirmations yet. As a result I could sent more coins then I owned, because for a sort while they were promoted to my balance. These transactions, with the 'false' coins weren't accepted by the network so eventually it doesn't go wrong but my wallet was having troubles afterwards. I repaired it, reloaded the blockchain, actually I don't recall what exactly I did but at some point all problems were gone.
I hope this makes any sense, and maybe contributes a bit in further improving the wallet, which seems a lot of work, so respect!
Good bug find. I'll see what I can find out. Edit: I think this is ok. Not sure exactly what you did, but I kept sending the same block of coins to myself. Before I got any confirmations. and eventually they all went through. Since you are sending to yourself these won't go to unconfirmed. Let me know if I have the scenario correct. The only difference was that I didn't send coins to myself but to another address in another wallet on another computer instead. This computer is located at work so it's on a different LAN as well. It's controlled with teamviewer. The receiving wallet is version 1.52. I would say that shouldn't make much of a difference but this was pretty much the exact scenario. And last night I actually managed to solomine a block of CAP with the 1.999beta version. I found only one block and it was accepted by the network so I guess this works just fine! I just tested 2 wallets 1.999 to a 1.999 the sent from the first went to the unconfirmed to the other, and left the first no problems. It is possible there was a bug in 1.52. I changed quite a few things in the transaction processing, so if there was an issue, it should be gone now. Thanks for the PoW test! |
|
|
|
|
Show Posts
