Awesome! And dash is supported out of the box!   |
|
|
|
hi all i was just wondering were i should unpack the bootstrap i just downloaded to get the wallet up and running
just to roaming dash folder or block folder inside that.
thanks for any help
Inside Dash folder itself https://github.com/UdjinM6/dash-bootstrap#usage  |
|
|
|
Hi Nrigo, The summary page has always shown transactions in and out AND all minted transactions (under recent transactions) until this upgrade. Has it been removed or do I need to switch something on?
The summary page layout is the same as the old version but not showing updates unless this has to be reordered somewhere as well.
UdjinM6 is more able to answer to you than me, because he released the last updates. Nope, not sure why there is such issue because nothing was changed in that part of code since 2.1.2: https://github.com/UdjinM6/Coin2.1/compare/v2.1.2-bugfix.3...masterAnd btw, mint txes appear on overview page as usual on my Mac here. Maybe it's some Windows issues? |
|
|
|
c2 wallet:
"error:transaction credtion failed"
i have 1100000 c2coins , i can only send 60000 c2coins once
Every wallet out there has limits like that - you can't fit too much inputs into one tx because 1) it will be too huge 2) it might take way too much time to verify tx like that. And the reason it happens here is you are probably sending coins that were staked inside your wallet and every staking is producing 2 (meaningful) outputs. So yes, the only option is to send in smaller chunks. |
|
|
|
connected now and mining - 3 connections.
That's because there are now few other wallets running 2.1.3.1 which allow you to connect properly. To get even better connectivity I would still advise to update. This will require full resync though but as yet another bonus besides better connectivity your wallet should start 5-10x faster after update.  |
|
|
|
Andreas Antonopolis says that centralisation due to ASICS is at an end. It peaked and is now on the wane towards decentralisation from here on in. (I saw him say it with my own eyes and heard him with my own ears ) Here he is . Unfortunately, this particular video fails a few moments into his answer and leaves a huge 20 minute silence gap till it recommences. Maybe Aleix will get a more complete version up soon. Hi toknormal, In fact he didn't seem worried about it...describing that like some kind of cyclic event due at technological developments, and the time will fix it. At the same time, I liked when he told the worries about "chinees power" could be due just at some kind of racism, because if this power were in Finland (maybe), people would not be so worried about it. |
|
|
|
Yeah 2.1.2 is not working it seems, no nodes? What caused this?
have to download the chain again sigh gonna take a few days.
 http://c2chain.info/bootstrapA couple of days ago, it only took me few hours syncing the wallet after downloading and using the bootstrap. I never used the bootstrap, trying that now. So... what was the outcome? did it worked for you? how much time did it take? Just curious to get some stats |
|
|
|
On another note here is what Adam Back proposed on twitter few hours ago: Halvening: if miners were concerned they can softfork difficulty down 50% pre and release at halvening. Harmless just speeds blocks for week https://twitter.com/adam3us/status/717023841529114625Not sure if he is serious or what... |
|
|
|
.... Bitcoin's halving is around the corner and there is a concern that this will create mempool transaction problems on Bitcoin's network on a larger scale then previously witnessed ... Why is the halving expected to increase Bitcoin traffic / mempool size? ... Some predict that after halving and no price increase some miners could turn their machines off and hashrate could drop because of that more or less significantly. That would be ok but bitcoin difficulty adjusts every 2016 blocks so miners who are still mining would have more work to be done to solve a block than it should be for a hashrate like that for quite a long time (normally 2016 is 2 weeks and with lower hashrate this timeframe grows). This would mean larger time between blocks which in its turn would mean more transactions waiting in line to get into the block which could lead for confirmation problems which could decrease the price which will make it unprofitable for more miners which will turn their miners off and there you go - "death spiral". However some say that that's not going to happen because either price would increase thanks to increased scarcity or because of press covering halving event or simply because miners rent their electricity ahead of a time and a) they have no choice but to mine because they already payed and b) they have made million $$ investments into mining and should have foreseen this situation already. I have no idea who is correct, so I'll just grab some popcorn and prepare for fireworks  |
|
|
|
Yeah 2.1.2 is not working it seems, no nodes? What caused this?
have to download the chain again sigh gonna take a few days.
http://c2chain.info/bootstrap |
|
|
|
Can anyone else connect to the C2 network now?
Mine says 0 active connections.
Can anyone else connect to the C2 network now?
Mine says 0 active connections.
Added all those nodes, but still have the same problem as you. I would advise to try 2.1.3.1 https://github.com/UdjinM6/Coin2.1/releasesPlease be aware of 2.1.3 changes though: Note: this release contains breaking changes to how block index is stored. You will HAVE TO resync blockchain from scratch either directly from network or by using bootstrap.dat (could take few hours). Make a copy of your current data folder in case if you decide to switch back. |
|
|
|
... At the moment we have one and only slot type and it costs 0.1 DASH. Having that in mind it would be too expensive to send back single instantX to each player at the current rate. We have talked about the sendtomanyix command here: https://bitcointalk.org/index.php?topic=421615.msg13712922#msg13712922We hope that it will be implemented at some point. ... One more issue is that we are not able to mix coins using dashd, so we can't send a lot of instantX transactions back to the users. Maybe that option exists but I am not aware of it? ... All this will be available in 12.1 https://github.com/dashpay/dash/pull/692 |
|
|
|
i'm getting no connections to the network, anyone else? Latest version.
2.1.3.1 or 2.1.2? EDIT: In any case try adding nodes manually: insert "addnode=IP" lines in Coin2.1.conf I added getpeerinfo output to c2chain http://c2chain.info/api/getpeerinfo, you can grab few IPs from there |
|
|
|
Are we Dash already again? EDIT: Yep |
|
|
|
Re: [ANN][Dish] Dish | I think the mods are risking a trademark issue with their renaming of the thread. It's more like system wide renaming of one word for another... I doubt it was find&replace in DB, more like a filter on output. Check... Dish / EDIT: was D a s h (no spaces) in the original message/ Yep, that's a filter Good job, bitcointalk mods! The next step is to completely filter out words you don't like and then start to censor the whole threads like /r/uᴉoɔʇᴉq already does!  There is also a [XMR] DarkFlarb and [ETH] Athereum however so we are not the only one..  |
|
|
|
FYI: http://c2chain.info/ updated to the latest version of iquidus explorer and reindexed from scratch + poloniex price/market info enabled + few bug fixes  |
|
|
|
Ok, I uploaded all blk* files from c2chain.info so you can simply extract them into Coin2.1 datadir (i.e. where your wallet.dat is located) and you should be fine with 2.1.3 without reindexing the whole blockchain. Might need to rescan though, not sure, but it shouldn't take that much time. https://transfer.sh/14T4QA/coin2.1.3.blk.tar (download should stay live for another 2 weeks) Thank you UdjinM6 for the wallet update and for your support. You made a very good work ! I'm currently testing the 2.1.3.1 release and I had to sync again after installation too because of the Blk file error. The last wallet release is loading very quickly using a clean wallet.dat file (with a few transactions only) and it looks to work fine, but I have to wait a few day to say if it stakes as well as the previous release. I will post a second feedback in a few days. Thanks! re blk error: If you just switched from 2.1.2 that's inevitable https://github.com/UdjinM6/Coin2.1/releases/tag/v2.1.3Note: this release contains breaking changes to how block index is stored. You will HAVE TO resync blockchain from scratch either directly from network or by using bootstrap.dat (could take few hours). Make a copy of your current data folder in case if you decide to switch back. re staking: should be the same as for 2.1.2, no code changed in that part https://github.com/UdjinM6/Coin2.1/compare/v2.1.2-bugfix.3...v2.1.3.1 |
|
|
|
Ok, I uploaded all blk* files from c2chain.info so you can simply extract them into Coin2.1 datadir (i.e. where your wallet.dat is located) and you should be fine with 2.1.3 without reindexing the whole blockchain. Might need to rescan though, not sure, but it shouldn't take that much time. https://transfer.sh/14T4QA/coin2.1.3.blk.tar (download should stay live for another 2 weeks) |
|
|
|
...
Only version 2.1.2.0 will start without error for me but it has stopped staking for some reason.
...
Because for 2.1.3+ you need to redownload/reindex blockchain first (hopefully only once). ...
It has been staking fine up until yesterday and can receive coins I withdraw from Bter. But no staking. And yes the wallet is unlocked.
Anyone else using 2.1.2.0 who can still get staked coins?
... Hold your mouse over the lightning symbol and it should say how much time (on average) you'll have to wait till next reward. Hold your mouse over the green checkbox and it should say what is the current difficulty - it's ramped up few last days imo because many started to see a bit more value and started to stake a lot. |
|
|
|
is it ok to run v2.1.0.0?
If anything until 2.1.3.1 is fixed, I would use 2.1.3.0, it opens quicker than previous versions and i think 2.1.0.0 had a problem with the debug log growing to gigantic file size The thing about 3.0 is you have to redownload the entire blockchain or use the bootstrap with it to sync up. The bootstrap is most likely quicker, there should be instructions on how to use it, it can be downloaded from http://c2chain.info/bootstrapDO you know if anyone is working on the client fix? Yes someone is working on it, as for whats wrong with 2.1.3.1, that is the work-in-progress version, it is not accepting the blkindex.dat(from the previous 2.1.3.0 version), 2.1.3.1 is useable, but you have to resync from scratch. UdjinM6 needs someone to sync 2.1.3.0(which had changes that actually required a total resync), and upload the blkindex.dat so he can analyze it. I would do this myself except my internet is really slow, comparable to dialup and it would take a few days to upload a file that size. I already have 2.1.3.0 sync'd and a blkindex.dat ready to go, but my internet issues are hindering me. Anyway, if someone does this for us, I'll give a bounty of 20,000 C2. Err... That's not what I meant. I meant let's see if someone else will have the same issue. 2.1.3.1 works comletely fine for me, so no, I'm not working on any fix. |
|
|
|
|
Show Posts
