hahaha of course, sorry my mistake, i was confusing the two :p but now that you mention it  i've always thought having a numerical return is a bit misleading. how about giving a firm indication of it's non-value? "proof-of-work" : NA, hmmm, i honestly can't think of a simple term to use.. |
|
|
|
limxdev ...
can i just transfer coins - then compile new wallet - then transfer back? ...
or is this a new blockchain? ...
#crysx
is new chain. need to import yr keys, then there's ya coins.. i just put the wallet.dat into new chains datadirectory, much ease of easeness. |
|
|
|
block 501 … let's see how she rides it out .. hopefully anyone who is using the first win qt has updated to the latest version for enhanced network power !! i believe the version here to be updated  https://github.com/LIMXTEC/B3-CoinV2/releases/(changing the default input size to 10, which will create more inputs for staking) |
|
|
|
It the last commit included? Today over 20 30 POS blocks... yes with the smaller split/combine thresholds |
|
|
|
Has the coin been taking over by a new Dev or something ? Clearly he knows what he is doing I am glad. I think I will buy some more b3 and start staking right away as it should have worked to begin with. So much staking time lost  now they're on a dead chain. what will happen with yobit ? TIP O'THE DAY. Do not buy on YoBit currently !! |
|
|
|
cool. i just moved my wallet.dat into the new coin directory and all is good. on an amusing note, staking info seems still incorrect getstakinginfo { "enabled" : true, "staking" : true, "errors" : "", "currentblocksize" : 1000, "currentblocktx" : 0, "pooledtx" : 0, "difficulty" : 0.00024414, "search-interval" : 1, "weight" : 3132585000, "netstakeweight" : 95, "expectedtime" : 0 } ,,,, and got my first stake a large quantity of those 0.005 inputs combined into one https://github.com/LIMXTEC/B3-CoinV2/blob/master/src/wallet.cpp#L26static int64_t GetStakeCombineThreshold() { return 5000 * COIN; } static int64_t GetStakeSplitThreshold() { return 1 * GetStakeCombineThreshold(); } .. with a coinsupply of 260k, 5k split/combines will lead to 52 inputs .. lol (except people won't have neat amounts of 5k so it will realistically be more if all coins were staking) i'm modifying my daemon to 100 (split/combine), but my coins have already staked |
|
|
|
my mistake, am compiling wallet now, i will post a mac qt a bit later current git needs that old chestnut to work $ chmod +x leveldb/build_detect_platform |
|
|
|
No there are actually people that are staking such small amounts:
2016/16/10 - 0.00068447 LOC which was an actual staking reward.
Such a transaction has approximately the same overhead than a single transaction of 10000 LOC. Now imaging adding 1000 of those small ones and having to pay 1.5+ LOC for the transaction fee. The tx fee will be more than the value of the tx. You will never be able to send the coins unless you add an input block to the mix of about 1.5 LOC so that you at least have a positive dust value for the tx.
txid please, that reward is pretty much the same that i have for POW blocks (0.00068448) here's example  do you realize that each tx value is 5.00068448 ? 02:24:56

Welcome to the Loco RPC console.
Use up and down arrows to navigate history, and Ctrl-L to clear screen.
Type help for an overview of available commands.
03:00:14

gettransaction 5d2d2ff92155cfb5009defe8d99435f4eab208a51bc77eafc941a40ffd584bc4
03:00:15

{
"txid" : "5d2d2ff92155cfb5009defe8d99435f4eab208a51bc77eafc941a40ffd584bc4",
"version" : 1,
"time" : 1476442800,
"locktime" : 0,
"vin" : [
{
"txid" : "892fc1e5bbb3653eb703390d49ca8be10b20c7e9f1596c8fa7e6b746e909e394",
"vout" : 0,
"scriptSig" : {
"asm" : "3045022100886050da7bfea591aa8c5f4adcbd182e4813a0d58691ef1fd9ef43f6fb0d667e02200646dd4d54eee325aa05ea6fa0e611cfb1c7db5cce01df8a34ce097b741d575b01 03c76ec2cb2011457a4dcc0478afd2f4f4d325891820c3b1331547aa70be14576d",
"hex" : "483045022100886050da7bfea591aa8c5f4adcbd182e4813a0d58691ef1fd9ef43f6fb0d667e02200646dd4d54eee325aa05ea6fa0e611cfb1c7db5cce01df8a34ce097b741d575b012103c76ec2cb2011457a4dcc0478afd2f4f4d325891820c3b1331547aa70be14576d"
},
"sequence" : 4294967295
}
],
"vout" : [
{
"value" : 0.00000000,
"n" : 0,
"scriptPubKey" : {
"asm" : "",
"hex" : "",
"type" : "nonstandard"
}
},
{
"value" : 5.00068448,
"n" : 1,
"scriptPubKey" : {
"asm" : "03c76ec2cb2011457a4dcc0478afd2f4f4d325891820c3b1331547aa70be14576d OP_CHECKSIG",
"hex" : "2103c76ec2cb2011457a4dcc0478afd2f4f4d325891820c3b1331547aa70be14576dac",
"reqSigs" : 1,
"type" : "pubkey",
"addresses" : [
"5svExsoYQrwLdrYQdbH5szR6onxHBrzj7E"
]
}
},
{
"value" : 0.00068447,
"n" : 2,
"scriptPubKey" : {
"asm" : "OP_DUP OP_HASH160 c6e899a49d0140be82e68648903e3a9b8c00b1f8 OP_EQUALVERIFY OP_CHECKSIG",
"hex" : "76a914c6e899a49d0140be82e68648903e3a9b8c00b1f888ac",
"reqSigs" : 1,
"type" : "pubkeyhash",
"addresses" : [
"69ByFdTC9RoaKKe6vryoxx1pQ5FxAPRpdA"
]
}
}
],
"amount" : -0.00068447,
"fee" : 0.00136895,
"confirmations" : 4787,
"generated" : true,
"blockhash" : "e9db9ec20feb156aadc57ab08b1955ad39ebfd125526c1e0462d6d87fa8ab5fb",
"blockindex" : 1,
"blocktime" : 1476442800,
"txid" : "5d2d2ff92155cfb5009defe8d99435f4eab208a51bc77eafc941a40ffd584bc4",
"time" : 1476442800,
"timereceived" : 1476442800,
"details" : [
{
"account" : "",
"address" : "5svExsoYQrwLdrYQdbH5szR6onxHBrzj7E",
"category" : "generate",
"amount" : 0.00136895
}
]
}
idk if there are any masternodes running, maybe they have a bunch of tiny pieces coming from stakers Yes you are right. It is very difficult and confusing to analyse without a proper block explorer. Maybe there will be a new one after the next version of the wallet (if there is a next version) how exactly the reward structure works and what the split is between POW and staking. the split/combine thresholds could be tweaked and the wallet would recombine them over time. |
|
|
|
The wallet just freezes when I try to send anything. I barely have to click on 'send' for this to happen. It doesn't matter what amount or whether the address is generated by the wallet.
one last thing to try if you're keen enough use a daemon, i have found them to be more responsive at times than the qt. you will have to do a lot of command line typing there doesnt seem an official release, so i have built one i couldnt actually build a static coind (bloody bitcoin nerds hate osx!!!), so the necessary dependencies are included in a sub-folder. it seems to work , fingers crossed.. https://drive.google.com/open?id=0B5j8d4FSc7drQ0k3dmI1bGlfOXc << not official !!! (i have tested this on 10.8, and will check on 10.11 a bit later if i remember on reboot :p) -- what you will need to do, .edit QubitCoin.conf, .start the daemon, .when it's in sync, try a send command. i have no idea what size your transactions will be, so you may as well start small (500 Q2C) and see if that works. then go bigger if you don't understand what you're doing, you're just going to have to be a good littly copy-pasta monkey and do it anyway. lol --- you will need to add some settings to your QubitCoin.conf file, if you dont have one, there is one in the zip, so add some stuff, then move to appropriate location edit QubitCoin.conf by adding rpcuser=makesomethingup rpcpassword=makesomethinguphereaswell how to find your datadirectory, first go to Application Support using this article http://www.syniumsoftware.com/support-article/how-do-i-navigate-to-the-application-support-folderthere should be a QubitCoin folder in Application Support, drag the conf file there. if you're using a different datadirectory this will complicate matters slightly, --- open Terminal, which is in Application/Utilities/Terminal commands you need to enter in terminal will be prefixed with a $
eg
$ ./qubitcoind & have removed them for ease of copy/pasting navigate to where you put the qubitcoind, in the finder show the folder cd [drag folder from finder to terminal] mine, for example, would be now start the daemon, with some extra stuff to hopefully help, these settings should depend on your ram, the below uses 1000mb for dbcache, feel free to ramp it up if you have loads of ram ./qubitcoind -dbcache=1000 -maxconnections=1000 & the daemon should now be starting/loading, once it is loaded you will hopefully be able to get interactions from it using the included qubitcoin-cli.exe how to send coins is ./qubitcoin-cli sendtoaddress Qaddresstosendtohere 500 if success, it should then give you a txid in response. when you want to stop the daemon -- if the QubitCoin.conf is not correct, you might get this Error: To use qubitcoind, or the -server option to qubitcoin-qt, you must set an rpcpassword in the configuration file: if you cant get any response from getinfo, you could just try sending coins and leave it to see what happens. you could always open your debug.log (in your datadirectory), it should open in Console and will update real time, it's output will hopefully give you an idea of where it's at. this sort of stuff means it's still syncing 2016-12-16 06:37:05 UpdateTip: new best=000000e8ef81e86b7c0f68318c818b6d5e8608287344c93f4f2a28e5550935fe height=2194086 log2_work=52.908581 tx=2577763 date=2016-12-16 06:33:57 progress=0.999993 cache=0.0MiB(20tx)
2016-12-16 06:37:05 UpdateTip: new best=00000335e22864535be4672b42d0e8c2f14fb4d4d3769a9565a8012873c12da6 height=2194087 log2_work=52.908581 tx=2577764 date=2016-12-16 06:34:13 progress=0.999993 cache=0.0MiB(21tx)
2016-12-16 06:37:05 UpdateTip: new best=000003954ad6717eded6f90fd2c782710a022732e7c88f185c95aca111a156bf height=2194088 log2_work=52.908581 tx=2577765 date=2016-12-16 06:36:28 progress=0.999999 cache=0.0MiB(22tx) if you are using a different datadirectory you will need to tell the coind, to start ./qubitcoind -datadir=draglocationhere & to do other things ./qubitcoin-cli -datadir=draglocationhere getinfo ===== for extra value, if succesful you can automate the send process this seems to work, it's a simple loop you enter into terminal the following should send coins every 10 minutes (as long as you're in the right folder), if successful you can change the amount of coins (5000 below), and time between sending (600 = seconds, 10 minutes) while true; do qubitcoin-cli sendtoaddress GXQ3CHQ6qy4u4j3exXdz9WWUqqovBzXydj 5000; sleep 600; done to end it [ctrl]+c or kill/close the Terminal window |
|
|
|
looks like a fork ?
zcoin getpeerinfo | grep startingheight
"startingheight" : 11643,
"startingheight" : 8197,
"startingheight" : 8197,
"startingheight" : 5134,
"startingheight" : 5770,
"startingheight" : 8197,
"startingheight" : 11643,
"startingheight" : 11643,
"startingheight" : 11643,
"startingheight" : 8197,
"startingheight" : 11643,
"startingheight" : 8197,
"startingheight" : 8197,
"startingheight" : 8197,
"startingheight" : 8197,
Nice to see you here, bumbacoin Its not a fork, more precisely - it is not a spontaneous fork, but a planned one. The nodes at 8197 are the ones which did not update code. There was a change in mining algo on that block. good to know, i set up wallet to only connect with higher chain, but it probably wasnt necessary then |
|
|
|
|
is there any way to speed up wallet start up?
ended up taking 30 minutes
2016-12-13 11:59:15 init message: Loading wallet...
2016-12-13 12:29:44 nFileVersion = 80702
|
|
|
|
|
looks like a fork ?
zcoin getpeerinfo | grep startingheight
"startingheight" : 11643,
"startingheight" : 8197,
"startingheight" : 8197,
"startingheight" : 5134,
"startingheight" : 5770,
"startingheight" : 8197,
"startingheight" : 11643,
"startingheight" : 11643,
"startingheight" : 11643,
"startingheight" : 8197,
"startingheight" : 11643,
"startingheight" : 8197,
"startingheight" : 8197,
"startingheight" : 8197,
"startingheight" : 8197,
|
|
|
|
Old Core
1. unlock your wallet
2. dumpprivkey SQ8Ai2WTTW28EfYZstDWe4u9QH2jyWMQk7
3. Note your Privkey (Example XFuXd6avu9KfN5K8oD3976VyzjEu8wD177bKPuMhBADBMet1F1wW)
New Core - Import your coins
3. Note your Privkey
4. importprivkey XFuXd6avu9KfN5K8oD3976VyzjEu8wD177bKPuMhBADBMet1F1wW
on 18th december ?? yes ? keep staking until then  ? … yobit has been down for me for hours . |
|
|
|
the new wallet connects well no longer attempts to use proxy on start up (can still use manually if you desire, just need to find a useful socks address) nodes to add to your DigitalPrice.conf addnode=24.37.43.158 addnode=98.115.147.74 addnode=80.110.108.166 .. for new source which has removed proxy connections as automatic startup see https://github.com/bumbacoin/DigitalPrice |
|
|
|
Many thanks for your help but none of the above worked. I spent all day sunday on this but to no avail.
Maybe if the new wallet is updated it might right itself as there was never a problem with the old wallet.
sorry i couldnt help :p do you see anything in your debug.log taht might shed any light ?? should be in your data directory with your wallet etc. |
|
|
|
|
Show Posts
