|
I have to say, I'm loving burst so far, but I have a long term concern.
You guys talk about things like how decentralized burst is, right alongside statements praising new developments like gpu mining.
I can't help but see those sorts of things as counter to each other in the long term. What, in the future, would prevent relative few whales from putting up massive rigs fast connected to a few petabytes of storage, with GPU's driving utterly ridiculous numbers of nonces? (working in IT for the last two decades, that sort of rig isn't really too hard to imagine, just damned expensive)
Meaning it's not so decentralized when you need a minimum of 100T of dedicated storage just to make a dent. You end up with pretty much bitcoin today, but without the userbase/value. So, I've gotta ask, if there's something in the economic model that accounts for this? Or are we just figuring expensive is good? (hopefully in terms of exchange rate too, right?)
|
|
|
|
|
dbt1033,
dude, you're going to give someone a seizure with that image.
|
|
|
|
What would it take? Would I have to sell out? I want to see this move forward. Think about it.
dbt1033, I would prefer that not be the case... Passionate investors are absolutely something we need. As for 8-bit, IF he wants to, I'm all for working with him to move this forward. BUT, I really don't care about mastertrader, or some other coin I don't own, and I'm not going to start. If 8-bit wishes to control himself, and be professional, I'm all for 8-bit. If instead he wants to continue to play games, drop out, name call, etc. Then I'm all for finding the next dev. (Which I'll explain in detail now) No, no. I don't need your apologies.
If you don't want to quote a result of your creativeness, what about focusing on bringing masteretarded back to this thread to let him explain why should I let him earn a single satoshi.
8-bit, Simply put, as far as all the arguing that's happened to date, I.DON'T.CARE... Moreover, I actually find the getting off topic and arguing over petty shit annoying. So, 8-bit, even if you're absolutely right in all of these petty arguments you've had in a very public way, there's an old saying that applies here... "Well, you're not wrong, but you're still an asshole." (and I don't even know if you're right or wrong, I simply don't care) We're here talking about 8bit, and how we can drive that to where we'd all like it to go. If people you've had disagreements with also make some coin here, who cares? You made your money too, and you get to put your mark on something successful. But don't answer me with justification as to why you're right, because I seriously don't care, these are things that don't involve me, nor most of us here. We'd just like to get to business, to make something great, and earn a few bucks along the way. What we'd like from you, is the same, and with THAT being the goal in mind, that's where you fall short in my eyes. Unprofessional. Again don't tell me who else is unprofessional, I'm not talking about them, nor their other coins and other communities, I don't care. You want to stick it to those that have wronged you? Man up, and get things done, this is where the opportunity is. Work with those of us that share this goal, and ignore the rest. Turn yourself into a multimillionaire (In fiat currency) with 8bit, without giving a fuck about who else might be holding some friggin coin. Which isn't your problem anyway.... Then when you do leave to move on to whatever the universe has in store for you, you're Bill Gates leaving microsoft with his billions a few years ago, as opposed to that guy who sold Bill Gates the code for DOS in 1981 for a few thousand dollars. If not, then bail, play a smaller role while we look to bring on a new dev, sell out and vanish, whatever works for you. But, not this shit, if you can't be professional, then it's time for you to go. So at this point, if you want to be the dev, which I guess is up in the air, please understand there is going to be an expectation for you to behave professionally. In this thread, for this coin, and in this community, no one wants to hear you whining and picking fights because you got screwed elsewhere. So I guess it's up to you, but seriously, if your goal is not to do what you can to make 8bit as successful as you can, with class and professionalism... If you can't get yourself together to see what's best for the community, and in turn yourself, regardless of your differences with others... Then I I'd have to say, lets find new dev... Because, that's the passion and expectation most of us here have, and I believe we need to absolutely expect that from anyone playing such a key role. TL;DR = Grow Up. |
|
|
|
|
So the sync took about 13 hours... Which is actually better than before, but I still think vast improvement is needed there.
That said, we could speed this up to something like 3 or 4 hours right now, if/when we start to push for usage of this wallet (or the next one, depending on direction of the coin) we generate a new bootstrap.dat. I think the one we're using now has something like 80k blocks in it, and the current chain is a bit over 175k.
BTW, anyone else notice the money supply passed 300k?
|
|
|
|
Ok, folks, sorry for the delay... But, I have indeed made this work with a slightly different revision of secp256k1... Sooooo, without further adieu, here are the steps to build a linux wallet on a fresh debian jessie install (32 or 64). Bare in mind, this is just for 8bitd, meaning no GUI, runs as a service. (Better for nerds, because if you intend on things like running a bunch of masternodes on a single box, pretty pictures take up memory) If there is enough demand, I'll see if I can cook up the QT recipe for everyone. - mkdir <directory you want this to live in>
- cd <that directory>
- sudo apt-get install build-essential libssl-dev libdb++-dev libboost-all-dev libqrencode-dev libminiupnpc-dev dh-autoreconf autotools-dev
- git clone https://github.com/bitcoin/secp256k1.git
- cd secp256k1
- git checkout d5b53aa81816214aa7c9e1095ff6ee1d4c13f9d2
- ./autogen.sh
- ./configure
- make
- sudo make install
- sudo ldconfig
- cd ..
- git clone -b fixed_sync https://github.com/8bit-dev/8bit.git
- cd 8bit/src/
- mkdir obj/crypto <--- The need for this step is easy enough to fix in the code isn't it? :p
- make -f makefile.unix -j2 "USE_UPNP=-"
- strip -s 8bitd
- mv 8bitd <where ever you want it to live>
- mkdir ~/.8bit
- cd ~/.8bit
- wget http://www.8-bit.party/static/bootstrap.dat.bz2 && bunzip2 bootstrap.dat.bz2
- vi/nano 8bit.conf <-- And create file contents
- /path/to/./8bitd
Oh, and I speak from experience here, do NOT try to compile this on a system with less than 1G of RAM.... At least it didn't work out well for me. Sooo, it's syncing now... and in the early going, it does indeed seem to be syncing the blockchain much faster... but I'm going to reserve all judgement on that until it finishes with the bootstrap file and has to pull from the network. |
|
|
|
new new wallet is version v1.4.5.0-g32a928e, correct?
That is correct. You should see the Urge Market menu item. As I only compiled it for craved (make -f makefile.unix)... I know not, of this "menu" of which you speak.  However, I do see a "market" directory in the datadir, that I don't think was there before. Anyway, I've got two new nodes up, one a masternode and one staking. Both are synced and seem to be running just fine. |
|
|
|
|
new new wallet is version v1.4.5.0-g32a928e, correct?
|
|
|
|
On one of the boxes it's failing to compile on, I JUST successfully compiled the old version of the 8bit wallet.
Which commit version you have successfully compiled? 01db6031e6506ac8d5779ec8a69889b1646b65de or bcf2b5f42f0b81dfe1e424f5aae96cdc44bbb794 Ummm... e69cf314d9390babcbc91cf20e7b8b7d8aaace26 Isn't that the current "master"? |
|
|
|
Now you need downgraded secp256k1
Make sure that downgraded version will fully overwrite current one and remember about ldconfig.
I totally did... here's specifically what I did for secp256k1, it's exactly what works to compile the old wallet. On one of the boxes it's failing to compile on, I JUST successfully compiled the old version of the 8bit wallet... Still can't compile the new code. |
|
|
|
You have cloned wrong branch (use -b fixed_sync).
Latest orig dev commit described as Tor updates /or something, fake anyway/ brought this crap you see.
I wish it were that easy... I git cloned via the following as per your posts... git clone -b fixed_sync https://github.com/8bit-dev/8bit.git |
|
|
|
So, as of yet, I have been unable to get this to compile at all... It continues to fail with the "recipe for obj/key.o", which obviously screams secp256k1. So I've tried compiling the new code with secp256k1 installed at both the latest git commit, and the infamous a1d5ae1 revision, still no compile love. I've tried this on fresh installs of both 64bit Ubuntu 14.04 server, and 32bit debian Jessie, and also an existing install of crunchbang++ (basically debian jessie), and that last box can successfully build the current released version of the 8bit wallet just fine... Here's the useful bits if you've seen it before... (this attempt was with the older revision of secp256k1, but I've tried with the new version too.. same result) Ideas? g++ -c -O2 -pthread -Wall -Wextra -Wno-ignored-qualifiers -Wformat -Wformat-security -Wno-unused-parameter -g -DBOOST_SPIRIT_THREADSAFE -DUSE_SECP256K1 -I/home/eightbit/8bit/8bit/src -I/home/eightbit/8bit/8bit/src/obj -DUSE_UPNP=0 -DENABLE_WALLET -I/home/eightbit/8bit/8bit/src/leveldb/include -I/home/eightbit/8bit/8bit/src/leveldb/helpers -DHAVE_BUILD_INFO -fno-stack-protector -fstack-protector-all -Wstack-protector -D_FORTIFY_SOURCE=2 -MMD -MF obj/main.d -o obj/main.o main.cpp
key.cpp: In constructor ‘{anonymous}::CSecp256k1Init::CSecp256k1Init()’:
key.cpp:30:25: error: ‘SECP256K1_START_SIGN’ was not declared in this scope
secp256k1_start(SECP256K1_START_SIGN);
^
key.cpp:30:45: error: ‘secp256k1_start’ was not declared in this scope
secp256k1_start(SECP256K1_START_SIGN);
^
key.cpp: In destructor ‘{anonymous}::CSecp256k1Init::~CSecp256k1Init()’:
key.cpp:33:24: error: ‘secp256k1_stop’ was not declared in this scope
secp256k1_stop();
^
key.cpp: In member function ‘bool CKey::SetPrivKey(const CPrivKey&, bool)’:
key.cpp:470:90: error: cannot convert ‘unsigned char*’ to ‘const secp256k1_context_t* {aka const secp256k1_context_struct*}’ for argument ‘1’ to ‘int secp256k1_ec_privkey_import(const secp256k1_context_t*, unsigned char*, const unsigned char*, int)’
if (!secp256k1_ec_privkey_import((unsigned char*)begin(), &privkey[0], privkey.size()))
^
key.cpp: In member function ‘CPrivKey CKey::GetPrivKey() const’:
key.cpp:489:105: error: cannot convert ‘const unsigned char*’ to ‘const secp256k1_context_t* {aka const secp256k1_context_struct*}’ for argument ‘1’ to ‘int secp256k1_ec_privkey_export(const secp256k1_context_t*, const unsigned char*, unsigned char*, int*, int)’
int ret = secp256k1_ec_privkey_export(begin(), (unsigned char*)&privkey[0], &privkeylen, fCompressed);
^
key.cpp: In member function ‘CPubKey CKey::GetPubKey() const’:
key.cpp:505:101: error: cannot convert ‘unsigned char*’ to ‘const secp256k1_context_t* {aka const secp256k1_context_struct*}’ for argument ‘1’ to ‘int secp256k1_ec_pubkey_create(const secp256k1_context_t*, unsigned char*, int*, const unsigned char*, int)’
int ret = secp256k1_ec_pubkey_create((unsigned char*)pubkey.begin(), &clen, begin(), fCompressed);
^
key.cpp: In member function ‘bool CKey::Sign(const uint256&, std::vector<unsigned char>&) const’:
key.cpp:527:134: error: cannot convert ‘const unsigned char*’ to ‘const secp256k1_context_t* {aka const secp256k1_context_struct*}’ for argument ‘1’ to ‘int secp256k1_ecdsa_sign(const secp256k1_context_t*, const unsigned char*, unsigned char*, int*, const unsigned char*, secp256k1_nonce_function_t, const void*)’
if (secp256k1_ecdsa_sign(hash.begin(), (unsigned char*)&vchSig[0], &nSigLen, begin(), secp256k1_nonce_function_rfc6979, NULL))
^
key.cpp: In member function ‘bool CKey::SignCompact(const uint256&, std::vector<unsigned char>&) const’:
key.cpp:551:131: error: cannot convert ‘const unsigned char*’ to ‘const secp256k1_context_t* {aka const secp256k1_context_struct*}’ for argument ‘1’ to ‘int secp256k1_ecdsa_sign_compact(const secp256k1_context_t*, const unsigned char*, unsigned char*, const unsigned char*, secp256k1_nonce_function_t, const void*, int*)’
if (int ret = secp256k1_ecdsa_sign_compact(hash.begin(), &vchSig[1], begin(), secp256k1_nonce_function_rfc6979, NULL, &rec))
^
key.cpp:551:17: warning: unused variable ‘ret’ [-Wunused-variable]
if (int ret = secp256k1_ecdsa_sign_compact(hash.begin(), &vchSig[1], begin(), secp256k1_nonce_function_rfc6979, NULL, &rec))
^
key.cpp: In member function ‘bool CKey::Load(CPrivKey&, CPubKey&, bool)’:
key.cpp:567:90: error: cannot convert ‘unsigned char*’ to ‘const secp256k1_context_t* {aka const secp256k1_context_struct*}’ for argument ‘1’ to ‘int secp256k1_ec_privkey_import(const secp256k1_context_t*, unsigned char*, const unsigned char*, int)’
if (!secp256k1_ec_privkey_import((unsigned char*)begin(), &privkey[0], privkey.size()))
^
key.cpp: In member function ‘bool CPubKey::VerifyCompact(const uint256&, const std::vector<unsigned char>&) const’:
key.cpp:631:10: warning: unused variable ‘fComp’ [-Wunused-variable]
bool fComp = IsCompressed();
^
key.cpp: In member function ‘bool CPubKey::IsFullyValid() const’:
key.cpp:653:52: error: cannot convert ‘const unsigned char*’ to ‘const secp256k1_context_t* {aka const secp256k1_context_struct*}’ for argument ‘1’ to ‘int secp256k1_ec_pubkey_verify(const secp256k1_context_t*, const unsigned char*, int)’
if (!secp256k1_ec_pubkey_verify(begin(), size()))
^
key.cpp: In member function ‘bool CPubKey::Decompress()’:
key.cpp:668:76: error: cannot convert ‘unsigned char*’ to ‘const secp256k1_context_t* {aka const secp256k1_context_struct*}’ for argument ‘1’ to ‘int secp256k1_ec_pubkey_decompress(const secp256k1_context_t*, unsigned char*, int*)’
int ret = secp256k1_ec_pubkey_decompress((unsigned char*)begin(), &clen);
^
key.cpp: In member function ‘bool CKey::Derive(CKey&, unsigned char*, unsigned int, const unsigned char*) const’:
key.cpp:710:84: error: cannot convert ‘unsigned char*’ to ‘const secp256k1_context_t* {aka const secp256k1_context_struct*}’ for argument ‘1’ to ‘int secp256k1_ec_privkey_tweak_add(const secp256k1_context_t*, unsigned char*, const unsigned char*)’
bool ret = secp256k1_ec_privkey_tweak_add((unsigned char*)keyChild.begin(), out);
^
key.cpp: In member function ‘bool CPubKey::Derive(CPubKey&, unsigned char*, unsigned int, const unsigned char*) const’:
key.cpp:729:106: error: cannot convert ‘unsigned char*’ to ‘const secp256k1_context_t* {aka const secp256k1_context_struct*}’ for argument ‘1’ to ‘int secp256k1_ec_pubkey_tweak_add(const secp256k1_context_t*, unsigned char*, int, const unsigned char*)’
bool ret = secp256k1_ec_pubkey_tweak_add((unsigned char*)pubkeyChild.begin(), pubkeyChild.size(), out);
^
makefile.unix:201: recipe for target 'obj/key.o' failed
make: *** [obj/key.o] Error 1
make: *** Waiting for unfinished jobs.... |
|
|
|
EDIT2: whats the situation with dependencies, how much work is it to get this building on Ubuntu?
I have not played with the code yet at all... That's going to have to wait for me to finish with my regular IT day job for today... BUT, from things I've posted previously... Your general steps to compile are LIKELY something like this... Again... !!!WARNING!!! This is totally untested, compile at your own risk, don't put real amounts of funding on this until you're sure it works... And if somehow this fucks you in some way, I told you so!- mkdir <directory you want this to live in>
- cd <that directory>
- sudo apt-get install build-essential libssl-dev libdb++-dev libboost-all-dev libqrencode-dev libminiupnpc-dev
- git clone https://github.com/bitcoin/secp256k1.git
- cd secp256k1
- git checkout a1d5ae1
- ./autogen.sh
- ./configure
- make
- sudo make install
- sudo ldconfig
- cd ..
- git clone https://github.com/8bit-dev/8bit
- cd 8bit/src/
- mkdir obj/crypto
- make -f makefile.unix -j2
- strip -s 8bitd
- mv 8bitd <where ever you want it to live>
- mkdir ~/.8bit
- mv boostrap.dat ~/.8bit
AGAIN... I make no guarantees this works... ever. Evar!!! But, I will absolutely be compiling this myself tonight (not even starting until after 10pm MDT), and I will update with what worked for me. EDIT: You might not need everything from *git clone https://github.com/bitcoin/secp256k1.git* to *cd ..*, OR you might need it but not the *git checkout a1d5ae1* step, depending on where 8-bit-party got with his code. I'll let you all know later. |
|
|
|
Whatta wishful thinking. You ask a new dev to accept risk of falling knives from old dev / blockchain abusers.
Be an optimist...life is so much more vibrant. I am committing 4k 8bit to a developer who can adopt this bastard. By adopt, I mean feed it, change diapers, love it for the rest of its life. Great! That's 5K 8BIT total now. Damn guys... I'm jealous. That 4k is higher than my entire stash. I've got technical skills, bandwidth, and I'll host useful things on a good VPS I have, but I have barely enough coins to run two masternodes (assuming they're going to be 1024 a piece at some point after the relaunch, I guess I could run 19 or 20 at the moment, if I had the computing power on hand). Question: So I've run as many as 8 masternodes at once, but that many seems to melt the VM running on my little old server in the basement. I've since reduced it down to 4 masternodes, and I'm staking the rest of my funds on a 5th wallet. If we're starting to run some masternode based elections for development goals, should I start building more masternodes again? Meaning, is the voting per masternode, thus more masternode=a greater say in things? |
|
|
|
|
Question for you all...
So I'm relatively new to burstcoin, and I've just started mining recently.
I'm using Uray's Burst Miner 1.1r4 on Ubuntu 14.04, and mining to pool.cryptomining.farm.
I haven't had any problems with the setup that I couldn't figure out, and I'm seemingly happily mining away... (at least my balance on the pool is growing)
The problem, if it is a problem, I don't know... Is when I watch the mining logs, for a specific round, it'll submit a nonce before it's done reading all my plot files, and thus for a specific round I might have 2 or 3 submissions. They say they are successful in the miner log, but some of the early submissions suck, and my balance for the round doesn't seem to improve a few seconds later when a better nonce submission is made. So, when my miner submits a few submissions for a given round, am I being credited with the best one? Is this a problem at all? Is there something I can do to avoid it?
Thanks in advance.
|
|
|
|
Next time you will see such case issue and let us know if it helps. I did the resendtx (it is mentioned above), it didn't help. Thanks. |
|
|
|
Tried running the original wallet with -rescan, and sending a resendtx command... 0 confirms, and nothing else can see the tx...
-rescan will not help here. It rescans blockchain for missing transactions of your addresses (useful when you use import bunch of importprivkey calls with rescan=false and forgot to switch to rescan=true with last one). Solution? Use -salvagewallet (note you will use account labels if you use them) or wait up to 5 days (since first transmission) to get your tx removed from mempool. That worked awesomely... Thank you sir. |
|
|
|
|
Hiya folks... Sooo, I've got a problem.
Moving some 8bit around between two of my own wallets.
Annnnnd, the transaction is visible on the sending wallet, but not on the receiving one. Nor is it visible on the blockchain.
Several blocks have gone by, and my money is seemingly just gone, as the sending wallet thinks it sent it. Even though it's been some time, and over 50 blocks, there are still 0 confirmations on it, for the single wallet that even sees it. None of my other wallets can see the transaction either.
I've also tried moving the wallet.dat to a different wallet... again money is gone, and it can't see the transaction on the new wallet either.
Tried running the original wallet with -rescan, and sending a resendtx command... 0 confirms, and nothing else can see the tx...
Anyone got any ideas?
It's a fairly good chunk of 8bit for me...
|
|
|
|
I just have to add to this... My first was a NES, which I still have, and still works.... So my view was something like this..  |
|
|
|
|
Good job on the new thread!
With the idea being to surf the line between a completely open forum, and avoiding the discussion falling into trivialities and bullshit, as it has too often before... Might we want to have one of those "community moderated" threads? Just throwing it out here..
|
|
|
|
Wouldn't it be better to create a new slack and exclude 8-bit-party? I don't think we need to create any conflict and crypto is always a P2P effort. I just PM'd with 8bit party and he said he is fine with this. He did good work to get the new website, github etc online and he has taken the coin to this point. He just doesn't want to do much development right now for whatever reason. If he will work with us and help us to get 8BIT off the ground now, we all benefit. I think that would be the best way, he has been honest with me today and is helping us. Lets give him a chance to help 8BIT transition now...? I say fuck him... But if the community wills his presence going forward, I promise to not set him off. But like he said there are other issues here and reasons he doesn't want to develop now (MTR etc..), so having him on 'the board' is a good idea, because he has knowledge and experience that can help. It just means he won't be designated as the main dev, which I don't think he wants anyway, it would be a team effort instead. 8BIT party, is this correct - is this way forward ok with you? I have no problems with this... If he's not holding the reins, his presence could help us all... Does that mean we're sticking with the existing slack? (which one should I request?) |
|
|
|
|
Show Posts
