so how can we get this coin going again?
anyone able to sync the wallet up?
Not until yesterday. addnode=92.31.187.182:1108
addnode=1.34.180.245:1108
Cheers Graham |
|
|
|
This update fixes blockchain issues
I'm curious and would like to reproduce the fix, how did you check that it is actually a fix for the blockchain issues? I'm not in a position to check anything ... Startup time: 07/07/15 10:43:27
Default data directory /home/gjh/.beecoinv2
Used data directory /home/gjh/.beecoinv2
dbenv.open LogDir=/home/gjh/.beecoinv2/database ErrorFile=/home/gjh/.beecoinv2/db.log
Bound to [::]:1108
Bound to 0.0.0.0:1108
Loading block index...
Opening LevelDB in /home/gjh/.beecoinv2/txleveldb
Transaction index version is 70508
Opened LevelDB successfully
LoadBlockIndex(): hashBestChain=6b5d3784d7e4d0fa7795 height=1399721 trust=17278333475265896 date=05/06/15 10:04:22
LoadBlockIndex(): synchronized checkpoint 00000d91aace98244561246182a310d7a7c58ff4b005596ca44a44f9f78219f1
Verifying last 2500 blocks at level 1
block index 27506ms
Loading wallet...
nFileVersion = 1000200
Keys: 102 plaintext, 0 encrypted, 102 w/ metadata, 102 total
wallet 566ms
Loading addresses...
Loaded 85 addresses from peers.dat 2ms
mapBlockIndex.size() = 1405921
nBestHeight = 1399721
setKeyPool.size() = 101
mapWallet.size() = 0
mapAddressBook.size() = 1
ThreadRPCServer started
Done loading
ThreadStakeMiner started
ThreadMessageHandler started
ThreadOpenConnections started
ThreadSocketHandler started
ThreadIRCSeed started
ThreadMapPort started
ThreadOpenAddedConnections started
ThreadDNSAddressSeed started
Loading addresses from DNS seeds (could take a while)
Flushed 85 addresses to peers.dat 61ms
connect() failed after select(): Connection refused
IRC connect failed
IRC waiting 71 seconds to reconnect
trying connection 199.83.128.136:1108 lastseen=371185.0hrs
1 addresses found from DNS seeds
ThreadDNSAddressSeed exited
trying connection 64.251.65.98:1108 lastseen=1.1hrs
GetMyExternalIP() received [83.104.61.47] 83.104.61.47:0
GetMyExternalIP() returned 83.104.61.47
AddLocal(83.104.61.47:1108,5)
refreshWallet
ipcThread started
connection timeout
connection timeout
trying connection 149.126.74.136:1108 lastseen=371185.0hrs
trying connection 64.251.65.98:1108 lastseen=1.1hrs
No valid UPnP IGDs found
connection timeout
connection timeout
trying connection 1.34.180.245:1108 lastseen=371185.0hrs
trying connection 176.109.240.33:1108 lastseen=3008.0hrs
connection timeout
connection timeout
trying connection 92.31.187.182:1108 lastseen=18.7hrs
connection timeout
trying connection 64.251.65.98:1108 lastseen=1.1hrs
connection timeout
trying connection 64.90.187.204:1108 lastseen=72.4hrs
connect() failed after select(): No route to host
trying connection 64.251.65.98:1108 lastseen=1.1hrs
connection timeout
trying connection 31.130.252.16:1108 lastseen=501.5hrs
connection timeout
trying connection 92.31.187.182:1108 lastseen=18.7hrs
connection timeout
trying connection 92.31.187.182:1108 lastseen=18.7hrs
connection timeout
trying connection 213.162.108.2:1108 lastseen=3060.8hrs
connection timeout
trying connection 5.9.56.229:1108 lastseen=931.0hrs
connect() failed after select(): Connection refused
trying connection 92.31.187.182:1108 lastseen=18.7hrs
connection timeout
trying connection 64.251.65.98:1108 lastseen=1.1hrs
connection timeout
trying connection 92.31.187.182:1108 lastseen=18.7hrs
connect() failed after select(): Connection refused
IRC connect failed
IRC waiting 138 seconds to reconnect
connection timeout
trying connection 64.251.65.98:1108 lastseen=1.1hrs
connection timeout
trying connection 176.37.195.36:1108 lastseen=231.4hrs
connection timeout
trying connection 1.34.180.245:1108 lastseen=799.4hrs
connection timeout
trying connection 92.31.187.182:1108 lastseen=18.7hrs
connection timeout
trying connection 92.31.187.182:1108 lastseen=18.8hrs
connection timeout
trying connection 64.251.65.98:1108 lastseen=1.2hrs
connection timeout
trying connection 92.31.187.182:1108 lastseen=18.8hrs
connection timeout
trying connection 64.251.65.98:1108 lastseen=1.2hrs
connection timeout
trying connection 92.31.187.182:1108 lastseen=18.8hrs
connection timeout
trying connection 77.38.15.148:1108 lastseen=3362.2hrs
connection timeout
trying connection 64.90.187.204:1108 lastseen=72.4hrs
connection timeout
trying connection 92.31.187.182:1108 lastseen=18.8hrs
trying connection 199.83.128.136:1108 lastseen=371185.0hrs
connection timeout
trying connection 31.130.255.16:1108 lastseen=132.3hrs
connection timeout
trying connection 149.126.74.136:1108 lastseen=371185.0hrs
connection timeout
trying connection 92.31.187.182:1108 lastseen=18.8hrs
connection timeout
trying connection 1.34.180.245:1108 lastseen=371185.0hrs
connection timeout
trying connection 1.34.180.245:1108 lastseen=799.4hrs
connection timeout
connection timeout
trying connection 64.251.65.98:1108 lastseen=1.2hrs
connection timeout
trying connection 92.31.187.182:1108 lastseen=18.8hrs
connection timeout
trying connection 92.31.187.182:1108 lastseen=18.8hrs
connection timeout
trying connection 64.251.65.98:1108 lastseen=1.2hrs
connection timeout
trying connection 1.34.180.245:1108 lastseen=799.4hrs
connection timeout
trying connection 64.251.65.98:1108 lastseen=1.2hrs
connection timeout
trying connection 31.130.255.16:1108 lastseen=132.3hrs
connection timeout
trying connection 64.251.65.98:1108 lastseen=1.2hrs
connection timeout
trying connection 31.130.255.16:1108 lastseen=132.3hrs
connection timeout
trying connection 112.5.180.220:1108 lastseen=501.5hrs
connect() failed after select(): Connection refused
IRC connect failed
IRC waiting 211 seconds to reconnect
connection timeout
trying connection 109.172.55.170:1108 lastseen=1.1hrs
connection timeout
trying connection 207.192.253.172:1108 lastseen=2988.7hrs
connection timeout
trying connection 64.251.65.98:1108 lastseen=1.2hrs
connection timeout
trying connection 176.37.195.36:1108 lastseen=231.5hrs
connection timeout
trying connection 92.31.187.182:1108 lastseen=18.8hrs
connection timeout
trying connection 89.151.165.144:1108 lastseen=2914.6hrs
connect() failed after select(): Connection refused
trying connection 92.31.187.182:1108 lastseen=18.8hrs
connection timeout
trying connection 31.130.255.16:1108 lastseen=132.3hrs
Does anyone have a synced node that has a BEE2 blockchain less than a month old? Cheers Graham |
|
|
|
BeeCoinV2 Windows Client as well as the Github has been updated to 1.0.2.
The version of LevelDB has regressed from 0.15 to 0.12, is that part of the fix? Cheers Graham |
|
|
|
Just a question on the solo mining capability of the new wallet. Will it also by reference drop the getwork protocol causing older miners not being able to mine solo and therefore only working with stratum pools?
Oooooh, good catch. I hadn't spotted that. I agree, such a strongly Bitcoin-specific orientation is inappropriate for an alt. It severely reduces the appeal of 0.10+ Core versions of the Bitcoin reference client, I shall have to reconsider the strategy because it doesn't look promising at this point. Cheers Graham |
|
|
|
A pure breed emulation of BitCoin in honour of one of the most important protagonists of BitCoin and cryptography.
I beg to disagree. An unambitious copy, differing only in a few user-facing strings, seems to fall rather short. Pushing the envelope might be a better way to honour Hal's contribution - base it on elements, kick some cryptographic ass. Cheers Graham |
|
|
|
A short progress report.I'm working my way through the commit history of elements, integrating some of the features into VCoin 0.11 ... What is Elements?Elements is a collection of experiments to bring more technical innovation to Bitcoin. What is Elements Alpha?https://github.com/ElementsProject/elements/tree/alphaElements Alpha is the Elements project's first experimental test chain. Compared to Bitcoin itself, it adds the following features: - Confidential Transactions
- Segregated Witness
- Relative Lock Time
- Schnorr Signatures
- Additional opcodes
- Deterministic Peg (pegged to Bitcoin's testnet currency).
- Signed Blocks
That's quite a shopping list. The items are too experimental to feature in Bitcoin right now, they might upset the applecart and could seriously diminish Bitcoin's value if things went badly wrong. VCoin has no such handicap to speak of and is an eminently suitable vehicle for offering innovative services enabled by these features. Some of the power-ups are easy to obtain because they are contained in a single commit, I can just cherry-pick the commit and merge it. Some are much more challenging, requiring extensive re-factoring from 0.10.2 to 0.11. Elements runs on its own Bitcoin-protocol testnet, the services haven't been exhaustively tested, nor does any trace of them appear in the wallet GUI. It's a shopping list of ingredients, not ready-meals. Cuisine has yet to happen. Cheers Graham
|
|
|
|
shame dev could have used his clever skills to make something legit and that would have worked out better hint look out for another coin
It's a slapdash copy'n'pasta job, it's most likely that the dev has been blissfully ignorant until now. Cheers Graham |
|
|
|
This is so wrong. PHx and masterdoge had like 800 ghs to 3 THs hash, this coin never had more than 60 ghs and was around 20-15 ghs for the first 5000 blocks. Something is wrong here. I am sure this coin doesn't have that exploit.
Sorry to disappoint:  hexx to the left, masterdoge to the right, darkcrave in the center. The exploit is masked from direct comparison by a spurious whitespace character at the end of each line and a regex remapping of values to variables, once the masking is reversed, the diff is fairly clear. The introduced variable names act as a useful telltale: https://github.com/search?utf8=%E2%9C%93&q=++++%2F%2F+If+Klen+%3E+PAD_SIZE%2C+the+key+is+really+SHA256%28K%29.+%2F%2F+&type=Code&ref=searchresultsJust a few affected coins. Which particular one is the most likely candidate for the role of “Typhoid Mary” is left to rampant speculation. Cheers Graham |
|
|
|
Hi, trying to build qt on ubuntu
I experienced that issue too. It was a blocker for a while. Just in case it works for you, try ./configure --with-incompatible-bdb --with-gui=qt5 --enable-hardening=yes - hardening is the ostensible default but you never know. I ended up editing src/Makefile, changing instances of -fPIE to -fPIC. Cheers Graham |
|
|
|
new thread?
Yes, old thread is: https://bitcointalk.org/index.php?topic=1057102.0;allmetadata: - block_time - 60
- category - launched w/o source
- date_founded - 2015-04-02
- description - welcome Creva Group Co., Ltd. Creva coin developed by Bitcoin algorithms, such as e-currency, creva coin has a mission to spread around the world and operates. In addition, the payment system with companies to use electronic coin shop in the real world are trying our best. Through international exchange listing and public mining and hope go even closer to you.
- distributionscheme - ico-pow
- expiration - extant
- incept - 2015-04
- name - CrevaCoin
- powscheme - scrypt
- premine - 86%
- protectionscheme - pow
- protocol - bitcoin
- source - https://github.com/crevacoin/creva
- symbol - CREVA
- thread - 1057102.0
- total_coins - 7200000000
- website - http://www.crevacoin.kr/
Cheers Graham |
|
|
|
hashmeter 0 khash/s
hashmeter 0 khash/s
https://github.com/jamescoineron/octane/pull/1hashmeter 1353 khash/s
hashmeter 1289 khash/s
That's on a Sandybridge i3 1.40GHz × 2/2, entry-level laptop. Blake2b is very quick, takes full advantage of onboard ASIC. A good choice for minimising GPU advantage over CPU, I've always thought. Cheers Graham |
|
|
|
|
Hmm, I'm bound to wonder if they're actually Kiwis or whether that's simply where they chose to register the organisation.
The woeful spelling in the website's text suggests the latter:
“Track your crytpo payment every step of the jorney for your peice of mind.”
Shoddy QA, not a good sign from a company.
Cheers
Graham
|
|
|
|
|
Show Posts
