Topic: ◈◈Bitcredit ◈◈ Migrating to UniQredit◈◈ - page 96. (Read 284526 times)

@bitcreditscc

there is a problem starting the daemon (probably this is the problem with qt also).
the daemon was started without blockchain.
the segmentation is at instantX transaction scanning

Reading symbols from ./bitcreditd...done.
(gdb) run
Starting program: /root/bitcreditd
Traceback (most recent call last):
  File "/usr/share/gdb/auto-load/usr/lib/x86_64-linux-gnu/libstdc++.so.6.0.19-gdb.py", line 63, in
    from libstdcxx.v6.printers import register_libstdcxx_printers
ImportError: No module named 'libstdcxx'
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[New Thread 0x7ffff0cfe700 (LWP 25472)]
[New Thread 0x7ffff04fd700 (LWP 25473)]
[New Thread 0x7fffefcfc700 (LWP 25474)]
[New Thread 0x7fffef4fb700 (LWP 25475)]
[New Thread 0x7fffeecfa700 (LWP 25476)]
[New Thread 0x7fffee4f9700 (LWP 25477)]
[New Thread 0x7fffedcf8700 (LWP 25478)]
[New Thread 0x7fffed4f7700 (LWP 25479)]
[New Thread 0x7fffeccf6700 (LWP 25480)]
[New Thread 0x7fffdffff700 (LWP 25481)]
[New Thread 0x7fffdf7fe700 (LWP 25482)]
[New Thread 0x7fffdeffd700 (LWP 25483)]

Program received signal SIGSEGV, Segmentation fault.
CheckBlock (block=..., state=..., fCheckPOW=, fCheckMerkleRoot=) at main.cpp:2990

100 Pi2 Banknodes would be 20x more decentralised than almost any other PoW currency.

As for hot air, yes it's not perfect, but right now DASH for example has about 80GH/s chundering away, which is what, equivalent to about 40000 Ti750's or something ludicrous? 40000 * 30W = 1.2 Megawatts. And that's not counting the rest of the system, all the less power-efficient AMD cards, CPUs etc - 3+ Megawatts is probably closer to the truth.

3MW @ $0.10/kW/h = $7200/day.
Miners get 1300 DASH/day which is currently worth about $3000.

So unless you're getting your power at under $0.05/kW you're not even breaking even on DASH mining. "But I get electricity for free!" - Uh huh, someone has to pay for it you freeloading oaf. 

Dog alone knows what the actual power consumption of the Bitcoin network is, ASICs or not I bet it's orders of magnitude worse than DASH.
Some basic Googling puts it at >200MW.

100 Pi's at <1W each seems rather more sensible... BCR can beat every other PoW currency in actual decentralisation for the cost of running a couple of light bulbs. Think about that hideously expensive energy delta as money going into backing BCR instead.  

And yes, because BNs will not be allowed to mine consecutive blocks, a low power ARM device would be just fine, there's no point wasting any more energy.

By design each user/dac is expected to have one or two BNs only, the reason people can afford 3+ is because we are all early adopters, but moving forward as the backing increases we'll likely see the distribution change. My reference to VPS is made simply because the vast majority of users prefer them over running local nodes. Mining uses 750MB per core.... the "hot air" was escaped the moment we proved we could distribute coins in a fashion that does does not reward wastage on VPS and asics. By "expensive" to run a node, you are still looking at mining as a competitive single way to actually get profit....basically a remnant of "hot air" mentality.

A single BN in say 450 total BNs @ and a BN payout of 8 BCR, mining reward 8 BCR would get 32 BCR per day. @ a price of 1c each, that is $0.32 per day , almost $10 a month. If you are running this off a local node, then it's pure profit . using a VPS for online reliability would be break even... see where i am going? For any activity in crypto to make sense, we need to have assured minimum values that can support the basics....so instead of funneling funding to power companies, amazon and AMD , it now goes to backing BCR.

We now have a functional chain that works off our everyday machines, meaning no additional costs for it's existence and once i throw in the last BN mining stuff, completely (well...reasonably) secure. And with every additional bid, the price only ever improves.

Let's be honest it impossible to mine right now on all your BNs when you got more then 8 and you're using 1 even powerful VPS.

1 BN mining uses 1GB Ram and 1 CPU core,  I'm trying to use for some time 2 BNs mining on 2 core CPU with 2 GB Ram and 4Gb Swap, both cores are fully used, but still I don't see any 4.05 BCR fees incoming. (bitcredit-cli setgenerate true 1   , 1 core per 1 BN) this is cold BN on VPS

So I'm using also few home hot BNs wallets  (not the same as these 2 on cold VPS) and these works, 4.05 BCR are incoming for every BN. I know that all should work on 1 machine but it would be too much expensive and we are not escaping from "backing hot air" this way ...

If in future banknode=1 will mean setgenerate true without giving any option, then we will be again backing a hot air, VPS sellers will be very happy instead of ASIC makers.

BTW. how it will work, Intel Atom core will be enough to start mining the same way as Intel i5 just giving smaller hashrate, how about roseberry ?

Trying a new windows wallet on another machine and got the same problem starting as many of you, didn't start even once.

Cold setup is an important security feature that we will keep. for now just use the typical setgenerate true. Later versions will take banknode=1 to also mean setgenerate true

I see.
Yes I knew BN mining would eventually be encouraged I just didn't know if there was an actual command to make the BN mine or just by simply running the QT. Also will a cold node setup work aswell? or does the BN need to be running with the wallet.dat holding the funds in order to mine?

015-09-19 16:14:01 Locking Banknodes:
2015-09-19 16:14:01 fEnableDarksend 0
2015-09-19 16:14:01 fLiteMode 0
2015-09-19 16:14:01 nInstantXDepth 5
2015-09-19 16:14:01 Darksend rounds 2
2015-09-19 16:14:01 Anonymize Bitcredit Amount 2000
2015-09-19 16:14:01 Secure messaging starting.
2015-09-19 16:14:01 Error opening file: No such file or directory (877)
2015-09-19 16:14:01 Failed to read smsg.ini
2015-09-19 16:14:01 No address keys loaded.
2015-09-19 16:14:01 Processed 0 files, loaded 0 buckets containing 0 messages.
2015-09-19 16:14:01 Secure messaging enabled.
GUI: libpng warning: iCCP: known incorrect sRGB profile
GUI: libpng warning: iCCP: known incorrect sRGB profile
GUI: libpng warning: iCCP: known incorrect sRGB profile
GUI: libpng warning: iCCP: known incorrect sRGB profile
GUI: libpng warning: iCCP: known incorrect sRGB profile
GUI: libpng warning: iCCP: known incorrect sRGB profile
GUI: libpng warning: iCCP: known incorrect sRGB profile
GUI: libpng warning: iCCP: known incorrect sRGB profile
GUI: libpng warning: iCCP: known incorrect sRGB profile
GUI: libpng warning: iCCP: known incorrect sRGB profile
GUI: libpng warning: iCCP: known incorrect sRGB profile
GUI: libpng warning: iCCP: known incorrect sRGB profile
GUI: libpng warning: iCCP: known incorrect sRGB profile
GUI: libpng warning: iCCP: known incorrect sRGB profile
GUI: libpng warning: iCCP: known incorrect sRGB profile
2015-09-19 16:14:03 GUI: "registerShutdownBlockReason: Successfully registered: Bitcredit Core didn't yet exit safely..."
2015-09-19 16:14:03

one of my wanting to try second wallets, that won't start has got this inside the debug.log.

how to get rid off this smsg.ini or not important

Slowly, people will start to get it.

@ pro, you know that the eventual system design will encourage every BN to participate in mining right? I tried running 8 off my 8 core box, no such luck. The computing requirements are getting higher, as such for a single core VPS i encourage running only one BN.

Full BN only mining will come in a few weeks, for now my focus has been debugging the existing material , fork resolution and fine tuning the bidding code. Over the next few days , the git will light up once again with more code and fixes as i start work towards 0.30.18

I'm confused. When I have a BN running do I setgenerate true or how is it "BN only mining"? also, are all your nodes running from the same machine? because i gave up yesterday trying to run more than 2 on my vps.

Anyone know how to launch eg. bitcoin-qt with a URI? I know it's possible because you can click on a bitcoin URI in a browser and it works, but I can't find how the browser passes the URI to the client... 

I'm looking for something like,  'bitcoin-qt --URI=' ...?

I've been telling people for 18 months that a single crappy old celeron could handle the entire Bitcoin blockchain with ease, and probably that of every other active altcoin simultaneously. They look at me (or type at me anyway) like I'm crazy for thinking that anything under a petawatt's worth of compute power could possibly cope.

Anyway, BCR's blockchain is currently humming along on a bit more than one crappy celeron, but not much - ("networkhashps" : 1,) - and I just squeezed over 300 txes into block 205593 and ... no issues, surprise. I shall be consolidating the rest of my BN payments shortly.  

Competitive PoW is utterly fucking daft.  


Also, it occurs to me that another aspect of BCR being, among other things, a (worlds first?) p2p hedge fund is that assuming the bid price follows to some extent the market price, any pumping will result in permanently locked in value.

BCR is one of a very few (Xaurum, backed by gold?) cryptocurrencies that can't be dumped to zero, assuming any of the underlying assets still have market value.

Likely


The reason i changed the format of payouts was to sort out the zero payments issue , lets wait and see the next payout block.

It seems to work, I get a 'Rescanning' popup with progressbar, but no new BCR address or BCR.  

Some old bids still in final.dat, maybe they haven't been 'processed?'

Quick word


Please everyone, build and run with wallet support. Many things in trhe client now depend on the wallet. I actually intend to reove the option of using without a wallet. Also use bdb 4.8 , some of the newer versions are completely incompatible.

Do a git pull, i just fixed the standard key import.

Tested with hundreds of keys from all 3 prefixes.

I'm not sure if we're BN-only mining yet but I've hit 4 blocks out of the last 23 with a quarter of my old laptop's i5.

getmininginfo:
{
"blocks" : 204388,
"currentblocksize" : 1000,
"currentblocktx" : 0,
"difficulty" : 0.00000002,
"errors" : "",
"genproclimit" : 1,
"networkhashps" : 19,
"pooledtx" : 0,
"testnet" : false,
"chain" : "main",
"generate" : true,
"hashespermin" : 4
}
.. which puts me at a mighty 0.35% of the total hash if that's valid data.

So, I have no idea.

core limitation is enforced in this update?

Yeah that's debug, still looking into why some keys are working and others arent, should have an answer by morning

17.1 (built on xubuntu 14.10) synced fine from scratch after I specified port=8878 in bitcredit.conf. (I had it set on another port previously.)

Sadly still can't redeem:
"Invalid private key encoding (code -5)"

edit: just closed he client and got this on stdout:
"before X....blah.....blah.......r after M......blah..... blah..........7" - where the before was the dash privkey.

Alas, trying to import the 'after' privkey also gave:
"Invalid private key encoding (code -5)" - BCR privkeys should begin with a 'K' ?

edit2:  banknode up and mining on 1 core.

I'll investigate this, but this update did not involve any changes to db related areas.