 Show Posts
|
|
Pages: [1] 2 »
|
|
I don't know anything about trucoin's new wallet dev team, but I assure You there is no hardfork possible without alert keys and checkpoint keys, so only thing he can change is graphics, text, and version number.
|
|
|
|
|
This is not bitbar problem, this is QT problem, that's why it cant be fixed by changing bitbar files. It affects all windows QT clients compiled in that time.
It should be fixed when new ver is relased based on newer QT.
problem:
-QT not responding
reason:
-incorrect windows shutdown while running QT
quick fix:
- run some other coin wallet once, than run bitbar-qt
permanent fix:
-recompile using new QT
or
-wait for new version.
|
|
|
|
|
Looks like Alien is right, the longest chain was not the one than main exchanges was on, I resynced checkpointing client to CCE and everybody should see checkpoint to old warning disappear soon.
connect=btb.cryptocoinexplorer.com
|
|
|
|
|
All problems: checkpoint to old and fork, are due to dynamic checkpointing off - I stopped vps for BTB zero-client and redirected dns-lookup to some pool.
I synced my home client to longest chain and i suggest doing the same :
connect=btb.ltcoin.net, or at least addnode=btb.ltcoin.net
DNS first node search has been redirected to some pool ,soon dns will be updated to btb.ltcoin.net as it proves to be the fastest one.
I run dyn-checkpointing on my private PC now, until I get my hands on some VPS.
|
|
|
|
|
Anybody in non-forum contact with digger?
I PM'd and mailed[gmail] Him.
He's BTB pool is on 0.4.1 BTB client and all blocks from this pool are now getting orphaned, its such a waste and I cant get to him.
OK!! He responded and upgrade is in the making.
|
|
|
|
|
Invest0r is gone for 2 weeks now.
If he is not back soon, we will start a little fundriser for 1Peters work to be rewarded.
|
|
|
|
I am now downloading the block chains and rebuilding the database on CCE.
I am having a hard time grabbing peers, was there also a network version change that would prevent the new client from connecting to older versions. (Unlikely, but I thought I should ask just in case)
Also,
Do you have plans to integrate Novacoin network hash rate calculation that was released in a recent Novacoin commit, into BitBar?
It would certainly help me out to have the developer patch the daemon, then to attempt to patch it myself, without the intimate knowledge of the Bitbar code base the developers have.
We can add hashrate calculator, but I believe hashrate is a very bad indicator for comparison of POW and POS-hybrid blockchains models security strength . |
|
|
|
Everything worked OK with the 0.4.1 update, but it was just a first stage of a 2-step update that couldn't be done in single step to avoid risk of forking. Second phase was not planned so quickly, but there was another issue found buy no one else than the PoS Creator : Sunny King. Thanks to His help and support, we were able to fix potential instability issue in the future. It was originally found and fixed by Sunny King in Novacoin, and was already implemented in BitBar, but He found we needed a different approach. 0.4.2 : - Sunny Kings's fix for P2Pool blocks modifier desynchronisation issue - Second stage reworking of alert system. Now updated. This is not a hard fork update, it will work with the current one, BUT : - There is a mandatory redownload of the blockchain, to make all of them identical. - notify your favorite exchange and pool with this, potential desynchronisation block should not happen between them, to avoid doublespend's , just in case of super bad luck! WIN32 BINARIESSOURCES |
|
|
|
Maybe your wallet have corruption. Try this: Export your private keys. Create a new blank wallet. Import your old private keys.
This. |
|
|
|
|
First try to rescan [bitbar-qt.exe -rescan]
Maybe your transactions were made during desynchronisation or safe mode, and were not sent to the network.
You can check it in transaction details in your transaction section.
if it doesnt help :
-backup C:\Users\Username\AppData\Roaming\Bitbar
-delete everything but bitbar.conf and wallet.dat
-download blockchain again.
Cheers. Bitbar team.
edit:
Those addresses are not shown on blockexplorer, because your transfer didn't hit the network.
|
|
|
|
Looks like the new account of TruCoin
Mr TruCoin never contacted me, I don't know him. All his posts and sites have no connection to development team. You really shouldn't be trolled that easy by so obvious troll. |
|
|
|
is there a link to download 0.4.1 source code?
seems git still 0.4.0
0.4.1 is being tested, should be on git any minute. |
|
|
|
- no rounding for PoS blocks, to address low PoS diff and those small PoS rewards What does 'no rounding' mean? Also, how are you in contact with the dev? And are you allowed to give his details? Not everybody has their bitbar clients connected. I think not everyone Know the 5% RoI on PoS. That makes PoS difficulty is very low. Low diff is why even small transactions can make PoS blocks after very small amount of time, and the reward is minimal. rounding is up to 2 decimals, rounddown. Super small rewards ale below rounding are not paid. ex: reward of 3.432353 is rounded to 3.43 reward of 3.439865 is rounded to 3.43 reward of 0.009234 is rounded to 0.00 |
|
|
|
My fault, I should have been clearer. I was just stating my concerns about a site that would put up a network hash rate that cannot be accurate. Just to take caution with the rest of their numbers...  Anyway, I am basically going to get around the POS/POW problem by setting up an extra database that will contain the POW difficulty for every block since its implementation. The explorers on CCE update every block when the daemon trips the blocknotify script. I will add the process of getting the POW difficulty for the block currently being mined, along with a couple of other bits of information. This should allow for an accurate hash rate calculation. The extra information is to allow the users of the getnetworkhash API to use time or blocks when defining how they want the network hash calculated.As of now the API only allows for blocks. In that case, You ARE on topic. sorry again. |
|
|
|
I would be careful about any site that gives network hash rates on any of the POW/POS chains. The calculations at best are a rough guesstimate as the difficulty difference between POS and POW blocks completely throws the difficulty part of the hash rate formula off. At best (Unless somebody has beat me to implementing a fix  ), one can try and grab an average of POW difficulty over the last 24 hours or more and use that as the difficulty in the hash rate formula. I have one fix thought out already, but I would rather come up with a different one. However, this fix is pretty much on the top of my list now, so I guess I will implement it on CCE sometime this week. No. Reward is based on difficulty. It is trivial to calculate, PoS found or not. PoS blocks are rising the difficulty, so hashrate is hard to determine without eliminating PoS blocks. I am not addressing rewards, but total network hash rate. Oh.. yea, sorry, but there is no hashrate on coinchoose. I assumed You are on topic. |
|
|
|
Hi!! I see you properly read diff of bitbar, but completely lost block reward. you can make and easy workaround: Calculate reward = 1/(diff/0,000244140625)^(1/6) ; and your problems will go forever. coin.block_reward = COIN / pow(coin.difficulty, 0.16666667) Also, You can set default sort to adjusted diff, because it is awesome! Thank You for this great site. That calc leads to a block reward of around .61, but I believe it is .16. You have a broken calc. diff: 14.03671291 14,03671291/0,000244140625 = 57494,376079 57494,376079^1/6 = 6,212564264 1/6,212564264=0,160964 That calc leads to a block reward of around 0.16 . power comes before division just paste it into excel or type it into science calc. try again edit: go: http://web2.0calc.com/paste: 1/(14.03671291/0.000244140625)^(1/6) or paste it straight to google https://www.google.pl/search?q=1%2F(14.03671291%2F0.000244140625)%5E(1%2F6)&oq=1%2F(14.03671291%2F0.000244140625)%5E(1%2F6)&aqs=chrome.0.57j58j0.1001j0&sourceid=chrome&ie=UTF-8 |
|
|
|
I would be careful about any site that gives network hash rates on any of the POW/POS chains. The calculations at best are a rough guesstimate as the difficulty difference between POS and POW blocks completely throws the difficulty part of the hash rate formula off. At best (Unless somebody has beat me to implementing a fix ), one can try and grab an average of POW difficulty over the last 24 hours or more and use that as the difficulty in the hash rate formula. I have one fix thought out already, but I would rather come up with a different one. However, this fix is pretty much on the top of my list now, so I guess I will implement it on CCE sometime this week. No. Reward is based on difficulty. It is trivial to calculate, PoS found or not. PoS blocks are rising the difficulty, so hashrate is hard to determine without eliminating PoS blocks. |
|
|
|
Yes, this page is wrong too. It is NOT official page. |
|
|
|
|
