is there any official date for swap, i bought around 25M for staking at simplepospool, after 45 days they released a note to withdraw all SHND as staking is not working so haven't received any extra, price almost reduced 50 percent now to sell them but still interested in holding as coin as future but please update community whats going on with project so we can follow
the swap is active now, see http://shndswap.stronghands.infoI am also afraid that why the price is dumping? the staking won't work as the total supply has been mined.
staking still works fine, currently 500k SHND /block reward |
|
|
|
|
update : the fork is running well,
some old outdated clients are still running, they need to update,
the explorer is still on old chain,
we will be communicating with exchanges today asking for them to open their wallets again.
reminder : new chain is supported only by v110 and v111 clients
if you are running v101 v103 v105 or anything else. you need to update and resync your copy of the chain.
getinfo
{
"version" : 1010100,
"protocolversion" : 70719,
"walletversion" : 61000,
"balance" : 0.00000000,
"Darksend_balance" : 0.00000000,
"blocks" : 5996,
"timeoffset" : 0,
"connections" : 37,
"proxy" : "",
"difficulty" : 25.65872907,
"testnet" : false,
"keypoololdest" : 1529683781,
"keypoolsize" : 1001,
"paytxfee" : 0.00000000,
"relayfee" : 0.00010000,
"staking status" : "Staking Not Active",
"errors" : ""
}
getblockhash 5900
d19795bad7fe709ed418d502677802947187c46e765b6c0441ceec863148c7f2
|
|
|
|
new v111 release now available at https://github.com/bumbacoin/Mirai-Master/releasesthis release brings forward the disconnection of older clients. if you are running v101 - v105 please update immediately. you will need to delete your copy of the blockchain and syncronise again from zero please come to discord for assistance. https://discord.gg/ByAyjW8-- the new chain is building nicely  we are over block 5630 and the difficulty is now adjusting properly. getblockhash 5630 49b7a6c20bd98f97ca671c7d5ca0be0bfae6f173fcf87db49de15bffb364aff4 the main explorer has not been updated yet. so please ensure you are on correct chain by coming into discord and asking. |
|
|
|
new release v110 is now available https://github.com/bumbacoin/Mirai-Master/releasesthis is a mandatory update as it will fork from the current chain at block 5400. . this client will disconnect from older clients at (GMT): Friday, June 29, 2018 6:00:00 PM
all older clients will be abandoned at this time.
with a Fork set for block 5400 currently block time is hard to predict, but we are working with a figure of 200 blocks/day, this gives approx 24 hours after disconnecting older clients to fork.PLEASE UPDATE YOUR CLIENTS IMMEDIATELY.annoyingly enough, the rate of blocks quadrupled after release of prior clients, bringing the fork block forward approx ~32 hours before guesstimate. the fork has happened !! |
|
|
|
Okay, so may be it's just me being thick but in case any one else encounters the problems I have I'll write this to help them, or for those smarter than me to ridicule.
* Installed Windows wallet, no connections to the Bumba network.
* Eventually found out it uses ports 20202 and 20222. Not sure which is for the mainnet and which for testnet, I found conflicting info on this so I forwarded both in my router. Once I've got the wallet synced and fully working I'll disable each in turn and find out which it actually needs.
* Still no connections to the Bumba network.
* From post No. 339 (by bumbacoin) in this thread it appeared I was on a fork - not sure how because I used the latest bootstrap from the link on the Bumba website.
* From post No. 338 (by ukmayhem) I moved everything other than .lock and wallet.dat to a temp directory, will delete that lot once everything is fully sorted.
* From post No. 606 (by linenoise) I opened a command prompt as Admin, navigated to the directory where the wallet .exe lives and entered "bumbacoin2-qt-win32-v1100.exe -addnode=167.160.36.13" (without quotes) and the wallet loaded and had 1 active connection showing when I moused over the "signal bars" in the bottom right corner. I'd tried the first IP in the list linnoise gave but that did nothing for me.
* Once it had that one active connection it started syncing from the network and gaining more and more nodes. Currently it's at 20 active connections (hasn't increased in a while so I suspect that's a max. number).
Will be waiting a while for it to fully sync but at least it looks like it's all working as it should :-)
I hope this helps some one else get started in the future.
Next onto figuring out how to install and make the Linux wallet work. My end goal is to have it running on my RPi2.
Cheers, Mike...
Thanks to bumbacoin, ukmayhem, linenoise and every one else who contributed to this thread, useful information in here and a lot of laughs. Thanks all.
EDIT: 20 isn't a max. No. of nodes, it's now up to 23.
hi  great work, i dont actually check this thread much come to discord for more regular attention. lol https://discord.gg/RnYQ3U3there's a slack channel, but i dont go there much as i have too many things running i will have to check the bootstrap out and see what sort of fork shenanigans may or may not be happening. |
|
|
|
we've just whipped up a new version that fixes annoying RPC bug, also changes default port due to some conflicts with vpn software to 14440 also rpc port has changed to 14441 because of this change it is recommended to modify your current set of addnodes in teh following way, basically doubling up and giving each the old (4444) new (14440) port numbers once everyone has switched over the old port number will be un-necessary addnode=138.68.166.56:4444
addnode=138.68.166.56:14440
addnode=138.68.152.14:4444
addnode=138.68.152.14:14440
addnode=139.59.170.63:4444
addnode=139.59.170.63:14440
addnode=138.68.161.9:4444
addnode=138.68.161.9:14440
addnode=45.77.102.10:4444
addnode=45.77.102.10:14440
addnode=41.57.17.48:4444
addnode=41.57.17.48:14440
addnode=41.190.31.8:4444
addnode=41.190.31.8:14440
addnode=81.169.239.249:4444
addnode=81.169.239.249:14440
addnode=140.82.37.219:4444
addnode=140.82.37.219:14440
addnode=14.202.249.149:4444
addnode=14.202.249.149:14440 This is not a mandatory update but will be useful to change over due to the port changes. |
|
|
|
our apologies, the first fix release v102 included an invalid checkpoint and causes clients to get stuck at block 544. this was caused by an unexpected blockchain re-org and caught us completely by surprise. there is now release v103 available here https://github.com/bumbacoin/Mirai-Master/releasesthis release fixes the possible exploit we found in the code, also the invalid checkpoint I added to the code  |
|
|
|
lol BUM it's BUMBA  |
|
|
|
this project is deaded?
hopefully yes, the code contains an exploit to generate lots of free coins. |
|
|
|
Hi,
I am gettting this error please help me!!!!
/mnt/mxe/usr/i686-w64-mingw32.static/qt5/bin/uic src/qt/forms/optionsdialog.ui -o build/ui_optionsdialog.h
i686-w64-mingw32.static-g++ -c -pipe -fno-keep-inline-dllexport -O2 -std=gnu++11 -fdiagnostics-show-option -Wall -Wextra -Wno-ignored-qualifiers -Wformat -Wformat-security -Wno-unused-parameter -Wstack-protector -fexceptions -mthreads -DUNICODE -D_UNICODE -DWIN32 -DENABLE_WALLET -DBOOST_THREAD_USE_LIB -DBOOST_SPIRIT_THREADSAFE -DQT_DISABLE_DEPRECATED_BEFORE=0 -DUSE_UPNP=1 -DMINIUPNP_STATICLIB -DSTATICLIB -DWIN32 -D_MT -DBOOST_THREAD_PROVIDES_GENERIC_SHARED_MUTEX_ON_WIN -DQT_NO_DEBUG -DQT_WIDGETS_LIB -DQT_GUI_LIB -DQT_NETWORK_LIB -DQT_CORE_LIB -DQT_NEEDS_QMAIN -Isrc -Isrc/json -Isrc/qt -I../mxe/usr/i686-w64-mingw32.static/include -Isrc/leveldb/include -Isrc/leveldb/helpers -I../mxe/usr/i686-w64-mingw32.static/include/boost -I../mxe/usr/i686-w64-mingw32.static/include -I../mxe/usr/i686-w64-mingw32.static/include/openssl -I../mxe/usr/i686-w64-mingw32.static/qt5/include -I../mxe/usr/i686-w64-mingw32.static/qt5/include/QtWidgets -I../mxe/usr/i686-w64-mingw32.static/qt5/include/QtGui -I../mxe/usr/i686-w64-mingw32.static/qt5/include/QtNetwork -I../mxe/usr/i686-w64-mingw32.static/qt5/include/QtCore -Ibuild -Ibuild -I../mxe/usr/i686-w64-mingw32.static/qt5/mkspecs/win32-g++ -o build/txdb-leveldb.o src/txdb-leveldb.cpp
In file included from src/script.h:18:0,
from src/core.h:11,
from src/main.h:8,
from src/kernel.h:7,
from src/txdb-leveldb.cpp:17:
src/bignum.h:57:24: error: invalid use of incomplete type 'BIGNUM {aka struct bignum_st}'
class CBigNum : public BIGNUM
^
In file included from /mnt/mxe/usr/i686-w64-mingw32.static/include/openssl/crypto.h:31:0,
from src/allocators.h:12,
from src/serialize.h:22,
from src/core.h:9,
from src/main.h:8,
from src/kernel.h:7,
from src/txdb-leveldb.cpp:17:
/mnt/mxe/usr/i686-w64-mingw32.static/include/openssl/ossl_typ.h:80:16: note: forward declaration of 'BIGNUM {aka struct bignum_st}'
typedef struct bignum_st BIGNUM;
^
In file included from src/script.h:18:0,
from src/core.h:11,
from src/main.h:8,
from src/kernel.h:7,
from src/txdb-leveldb.cpp:17:
src/bignum.h: In constructor 'CBigNum::CBigNum()':
src/bignum.h:62:21: error: 'BN_init' was not declared in this scope
BN_init(this);
^
src/bignum.h: In copy constructor 'CBigNum::CBigNum(const CBigNum&)':
src/bignum.h:67:21: error: 'BN_init' was not declared in this scope
BN_init(this);
^
src/bignum.h:68:30: error: cannot convert 'CBigNum*' to 'BIGNUM* {aka bignum_st*}' for argument '1' to 'BIGNUM* BN_copy(BIGNUM*, const BIGNUM*)'
if (!BN_copy(this, &b))
^
src/bignum.h:70:31: error: cannot convert 'CBigNum*' to 'BIGNUM* {aka bignum_st*}' for argument '1' to 'void BN_clear_free(BIGNUM*)'
BN_clear_free(this);
^
src/bignum.h: In member function 'CBigNum& CBigNum::operator=(const CBigNum&)':
src/bignum.h:77:30: error: cannot convert 'CBigNum*' to 'BIGNUM* {aka bignum_st*}' for argument '1' to 'BIGNUM* BN_copy(BIGNUM*, const BIGNUM*)'
if (!BN_copy(this, &b))
^
src/bignum.h: In destructor 'CBigNum::~CBigNum()':
src/bignum.h:84:27: error: cannot convert 'CBigNum*' to 'BIGNUM* {aka bignum_st*}' for argument '1' to 'void BN_clear_free(BIGNUM*)'
BN_clear_free(this);
^
src/bignum.h: In constructor 'CBigNum::CBigNum(signed char)':
src/bignum.h:88:49: error: 'BN_init' was not declared in this scope
CBigNum(signed char n) { BN_init(this); if (n >= 0) setulong(n); else setint64(n); }
^
src/bignum.h: In constructor 'CBigNum::CBigNum(short int)':
src/bignum.h:89:49: error: 'BN_init' was not declared in this scope
CBigNum(short n) { BN_init(this); if (n >= 0) setulong(n); else setint64(n); }
^
src/bignum.h: In constructor 'CBigNum::CBigNum(int)':
src/bignum.h:90:49: error: 'BN_init' was not declared in this scope
CBigNum(int n) { BN_init(this); if (n >= 0) setulong(n); else setint64(n); }
^
src/bignum.h: In constructor 'CBigNum::CBigNum(long int)':
src/bignum.h:91:49: error: 'BN_init' was not declared in this scope
CBigNum(long n) { BN_init(this); if (n >= 0) setulong(n); else setint64(n); }
^
src/bignum.h: In constructor 'CBigNum::CBigNum(long long int)':
src/bignum.h:92:49: error: 'BN_init' was not declared in this scope
CBigNum(long long n) { BN_init(this); setint64(n); }
^
src/bignum.h: In constructor 'CBigNum::CBigNum(unsigned char)':
src/bignum.h:93:49: error: 'BN_init' was not declared in this scope
CBigNum(unsigned char n) { BN_init(this); setulong(n); }
^
src/bignum.h: In constructor 'CBigNum::CBigNum(short unsigned int)':
src/bignum.h:94:49: error: 'BN_init' was not declared in this scope
CBigNum(unsigned short n) { BN_init(this); setulong(n); }
^
src/bignum.h: In constructor 'CBigNum::CBigNum(unsigned int)':
src/bignum.h:95:49: error: 'BN_init' was not declared in this scope
CBigNum(unsigned int n) { BN_init(this); setulong(n); }
^
src/bignum.h: In constructor 'CBigNum::CBigNum(long unsigned int)':
src/bignum.h:96:49: error: 'BN_init' was not declared in this scope
CBigNum(unsigned long n) { BN_init(this); setulong(n); }
^
src/bignum.h: In constructor 'CBigNum::CBigNum(long long unsigned int)':
src/bignum.h:97:49: error: 'BN_init' was not declared in this scope
CBigNum(unsigned long long n) { BN_init(this); setuint64(n); }
^
src/bignum.h: In constructor 'CBigNum::CBigNum(uint256)':
src/bignum.h:98:49: error: 'BN_init' was not declared in this scope
explicit CBigNum(uint256 n) { BN_init(this); setuint256(n); }
^
src/bignum.h: In constructor 'CBigNum::CBigNum(const std::vector<unsigned char>&)':
src/bignum.h:102:21: error: 'BN_init' was not declared in this scope
there is still some support for the other release (102o) to make other stream of openssl, i think this will work, but i havent used it myself make MXE_PLUGIN_DIRS=/plugins/examples/qt5-freeze/openssl .. but i've just noticed they've updated to gcc5 , (recent for me ) , so that may make newer compiled deps incompatible with older ones if they were compiled with gcc4 .. alternative method is to overwrite your local copy of openssl.mk with the contents of the https://github.com/mxe/mxe/blob/master/plugins/examples/qt5-freeze/openssl.mk |
|
|
|
|
just rebuilt the daemon to v4033 (with bdb 5.3.28)
downloaded chainfiles.zip
but the daemon keeps giving
: Error opening block database.
Please restart with -reindex or -reindex-chainstate to recover.
no useful information in the debug
-
edit.
not sure what happened, but eventually it worked after deleting everything for th third time.
maybe i'd left an invisible file in the datadirectory
|
|
|
|
-- -- -- -- -- -- -- -- -- -- -- -- -- -- --
anyone have any recommendations to reduce cpu usage?
this is particularly for a daemon hosting a remote xnode.
it generally sits around 100% .
edit.
lolz now it's using less than 3% and prev was over 100%,
only thing i did was
setup cronjob to hourly wipe debug.log
and
start it up with -disablewallet
then shut it down,
and restart normally again.
it might be that usage builds up over time? and will peak again in a few hours??
so it built back up to 100% usage, have lodged an issue no github to hopefully get a reply |
|
|
|
Whats going on with this coin? I'm very interested but I've been hearing rumours of supply discrepancies...
I don't want to break out red text.
Edit: Getting to the bottom of this, may be FUD relating to a known FUDDER.
lolz. we here at bumbacoin international love BIG RED TEXThttps://bitcointalk.org/index.php?topic=1397815.0 |
|
|
|
I have xnode on linux and my debug.log was increased to 16Gb till server has down. I don't find command to switch off this log. How?
WoW  debug.log is just a log file you can delete it! Of course, only if you have an access to server every day. three possibilities. 1. use -printtoconsole=1 on startup or printoconsole=1 in hexxcoin.conf this will funnel all data onto the console rather than debug.log 2. you could do a cronjob regularly to wipe it 0 * * * * echo '' > /wherever/.hexxcoin/debug.log 3. funnel the data to oblivion, cd /wherever/.hexxcoin rm -f debug.log && ln -s /dev/null debug.log -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- anyone have any recommendations to reduce cpu usage? this is particularly for a daemon hosting a remote xnode. it generally sits around 100% . edit. lolz now it's using less than 3% and prev was over 100%, only thing i did was setup cronjob to hourly wipe debug.log and start it up with -disablewallet then shut it down, and restart normally again. it might be that usage builds up over time? and will peak again in a few hours?? |
|
|
|
https://twitter.com/CryptoBridge/status/989395061874900992CryptoBridge @CryptoBridge Following Following @CryptoBridge More ANNOUNCEMENT: $QDP (@QuDexPay) market is now closed indefinitely. As the chain is stuck and forked multiple times, we have no choice but to close until contact is made with us by the development team.
|
|
|
|
Dear Friends,
I have question,
one year ago i got 30Million SHND, and i have them in CoinExchange.io
i heard about sowap, Do i need to do anything?
please help me
thanks
You must continue to keep them even further - on the stock exchanges, incineration will happen automatically. After that you can install a masternodes on your computer and begin to get a good profit. Plys86 you are incorrect. the swap will be public, you will need to send coins to swap. await further news |
|
|
|
The real problem is the same one I posted about two months ago, when the total supply was 11 trillion and the price was .000005. The supply is ridiculous and still growing at astronomical rates. Literally added another 8 trillion coins in less than two months.
inflation has been curbed for the moment, we will stay at 19 trillion for the next while |
|
|
|
|
transactions showing in grey are normally orphans or invalid transactions,
an orphan is a stake that is rejected by the network,
an invalid transaction maybe caused by the fact we have had planned and unplanned forks - any transactions on those chains are invalid on the real chain.
please join the discord server and the #wallet-help-chat channel for assistance.
|
|
|
|
|
Show Posts
