[ANN][RDD] Reddcoin The Social Currency [PoSV] Electrum Wallet 1.0.2 - page 104.

eightspaces

full member

Activity: 126

Merit: 100

Ok.Win wallet v112 working as expected here, any ETA on the Mac wallet update plz? Need it

wookie85

newbie

Activity: 6

Merit: 0

Hmm i update the wallet, put back old wallet.dat and it works but still comunicate that "0 hours behind".

feeleep

legendary

Activity: 1197

Merit: 1000

~~anyone able to share correct blockchain?~~ - nevermind - after restarting several times it started to work...

https://www2.coinmine.pl/rdd/ - updated and ready to work

lucazane

legendary

Activity: 1198

Merit: 1000

POOL UPDATED

http://rdd.theblocksfactory.com/ updated , ready to mine !

the 7500 Reward for the finder of the block is still active and automatic (you don't need to do anything like some other pool require sending a message or something ...)

InCoinsWeTrust2

newbie

Activity: 14

Merit: 0

http://redd.incoinswetrust.com updated to last fix and running

ReddCoin

full member

Activity: 159

Merit: 100

Hi everyone,

We are back with the fix!

A new version of the Reddcoin wallet is available to download. You will have to delete and redownload the blockchain. This download is mandatory.

Windows Wallet v1.1.3
https://github.com/reddcoin/reddcoin/raw/master/release/download/v1.1.3/reddcoin-qt-v113-win.zip

Mac wallet v1.1.3
http://blockexplorer.reddcoin.com/download/v1.1.3/reddcoin-qt-v113-mac.zip

To update please follow these instructions below:

1) Please make sure you're using 1.1.3 and the wallet app is closed.
Windows: Navigate to C:\Users\USER NAME\AppData\Roaming\Reddcoin and BACK UP your wallet.dat file by making a copy of it and moving it to a secure location.
Mac: Navigate to ~/Library/Application Support/Reddcoin and BACK UP your wallet.dat file by making a copy of it and moving it to a secure location.

2) Now that you have your wallet.dat file backed up. Please remove the rest of the contents of the Reddcoin folder and keep it in a safe place for the time being. You do not need to delete it until you've confirmed wallet 1.1.3 is working.

3) Open the new wallet version 1.1.3 and allow it to sync with the network. This will take some time.

4) Once the wallet has synced it will be empty. Please close the wallet and place a copy of the backed up wallet.dat file back into the Reddcoin folder.

5) Open the wallet again and voila, you are done!

WARNING: DO NOT send your wallet.dat file to anyone!

hash.so

full member

Activity: 126

Merit: 100

Hash.so has been upgraded and you can start mining:

https://rdd.hash.so/

(most other places haven't upgraded yet, so if you withdraw coins it will take a while for them to show up anywhere)

Sarahiko

hero member

Activity: 772

Merit: 500

Any update on wallet when will it get fix RDD are going up in price as we speak, more and more are mining.

taken2

member

Activity: 114

Merit: 10

ReddCoin mine is up again! Updated to newlatest git version so You can again mining and get coins!

RDD p2pool
Reddcoin P2Pool - STATUS: UP
Pool URL: http://taken.pl:9344
Username: Reddcoin Address
Password: Anything
Algorithm: Scrypt
Don't use an exchange address - Use your wallet address!

lxjtian

full member

Activity: 201

Merit: 100

This annoys me to no end and it annoys me that there needs to be a bounty to fix this because you people are incapable.

I am sorry, but you would think that forking your own Litecoin derivative wouldn't be the job you or your team would take on - if none of you had real world and ongoing experience in writing, managing and debugging C++ source code.

I am sorry this is pathetic and only proves that you're not doing a damn thing right with all that IPO money you received. Between this b.s. and the community around here having to do everything in terms of creating the tech that is supposed to be your team's job - this is an embarrassment.

Upping the bounty by any substantial amount means nothing other than you people obviously need to think about putting some real developers on your payroll. There's oDesk! There's Elance! There's Guru etc. etc. hire someone with a resume, experience and feedback and pay em' a real fucking wage!

This doesn't bode well pertaining to the point that you are going to be able to finish your prescribed plans i.e. API and services in any reasonable amount of time.

Was this all supposed to be some kind of joke? Release a master plan, but then fall back onto the community for everything you people are supposed to be doing?

I don't get it. I really don't. But you know what I can tell you one thing. I hope to god that with all the services people are working on creating around this coin (that is supposed to be your job and your plan) are compensated by you for their time and effort with a substantial amount of Redd... If it ever even survives these setbacks.

If it isn't one thing it's another with these coins, these exchanges, these services. If you aren't up to completing the task then you get someone on board with you who is before you decide to launch something as major as what you did! Amateur hour everywhere in this space and it's getting really, really annoying.

Rant over!

kintarooo

newbie

Activity: 13

Merit: 0

it is weird, coin was getting up and up.... Huh

hash.so

full member

Activity: 126

Merit: 100

I have a working code ready, but we need to work this out with the pools, or else we will just fork the coin n-times. Please join #reddcoin on freenode so we can figure out how to proceed.

Mathy

full member

Activity: 130

Merit: 100

To anyone trying to fix this problem: you need to also accept all the blocks < 6000 as they are since they were created pre-V1.1 fork and we don't have the code for that anymore afaict. The code that you had at commit 737fa08500bc2933ceb61d62d77f5408cd0ab040 will work I think. It's just that the genesis block isn't accepted by the CheckProofOfWork function when it is being called from ReadBlockFromDisk. I tried to make the necessary changes but don't have any time left. If it's not fixed by this evening I will try some more but I hope someone can fix the issue using this information in the mean time (and shares part of his bounty Grin

)

LeChatNoir

hero member

Activity: 699

Merit: 501

Coinpanion.io - Copy Successful Crypto Traders

https://www.cryptsy.com/coinvotes/

Craptsy recently added this future go vote now before everybody know this.

CrunchHarder

newbie

Activity: 42

Merit: 0

In bool CBlock::CheckBlock you could just

if nHeight <44877 return true;

at line 2152. You'd basically be accepting the blockchain up to that point.

Then checkpoint block 44877.

allcrypt

sr. member

Activity: 350

Merit: 250

Hehe. Was just doing some routine maintenance and came across:

"difficulty" : 599100784244695735335886766823493108010521318465388115920945152000.00000000

Figured I'd come here and see whats up. That would explain it Wink

CrunchHarder

newbie

Activity: 42

Merit: 0

Quote from: nightengale on March 05, 2014, 10:50:19 PM

Ok... At this point your website isn't even working.

Haha - how embarrassing, we forgot the DNS record. Thanks for pointing it out!

Our new Reddcoin pool https://rdd.crunchharder.net is _really_ available this time! (or at least it will be in a few minutes when the DNS changes have propagated)

steyast012

member

Activity: 90

Merit: 10

Quote from: DynamicDK on March 05, 2014, 03:21:14 PM

Everyone go vote on this. Don't rely on everyone else, and expect it won't matter if you do or not. It DOES matter. This isn't a huge election...the winner(s) will be separated by 1 or 2 digits most likely.
If you want this coin to go up, it is VITAL that it gets listed on more exchanges, and hopefully can get on a more stable one.

VOTE VOTE VOTE

Bter
https://bitcointalksearch.org/topic/annvote-new-coins-on-btercom-which-new-coin-should-bter-add-in-next-week-502363

VOTE VOTE VOTE

BTC38
https://bitcointalksearch.org/topic/poll-lockedill-start-a-new-post-soon-501963

VOTE VOTE VOTE

Don't be lazy!

+10000

Render

newbie

Activity: 6

Merit: 0

Quote from: ReddCoin on March 05, 2014, 11:40:35 PM

Hi everyone,

We are still working on a fix but we need some help. Here is what I posted in the developer forum. It's time to call your C++ professional friends so they can get 1 easy BTC.

While this is happening, nobody will lose their coins as we will start back at block 44877 when we have a fix. We hope to release the final fix in the next 24 hours. We will keep you up to date with the latest development.

Thanks

Reddcoin

Hi

We need some help with Reddcoin. We had a bug in our code, 2 lines were commented so the verification of block we're not done properly.

https://github.com/reddcoin/reddcoin/commit/88fc5fe0bf522e384b7aebfebced12b75e207e80

Someone exploited that error and he was able to grab 7k block in 1 hours. We were able to delete those block but we still need to use the block before 44877, and fix the bug for future block.

What we need to do is this. We need to get nHeight in this function so we can ask the code to check only after block 44877.

in main.cpp, function

bool CBlock::CheckBlock(CValidationState &state, bool fCheckPOW, bool fCheckMerkleRoot) const

I need to get access to the nHeight of the block and that's it to fix the problem.

You can look at our source code to make some test at

https://github.com/reddcoin/reddcoin

1 BTC bounty for anyone who can fix this.

Thanks

Reddcoin

Try this:

add parameter to:

Code:

bool CBlock::CheckBlock(CValidationState &state, bool fCheckPOW, bool fCheckMerkleRoot) const

Such that it becomes:

Code:

bool CBlock::CheckBlock(CValidationState &state, bool fCheckPOW, bool fCheckMerkleRoot, CBlockIndex* pIndex) const

Then change the one call of it (line 1645 in main) from:

Code:

    if (!CheckBlock(state, !fJustCheck, !fJustCheck))

to:

Code:

    if (!CheckBlock(state, !fJustCheck, !fJustCheck,pIndex))

Then remove (lines 2146 to 2151 in main):

Code:

    int nHeight;
    map::iterator mi = mapBlockIndex.find(hash);
    if (mi != mapBlockIndex.end())
         nHeight = (*mi).second->nHeight;
    else
        nHeight = 0;

And change (line 2153 in main):

Code:

    if (fCheckPOW && nHeight > 44877 && !CheckProofOfWork(GetPoWHash(), nBits))

To:

Code:

    if (fCheckPOW && pIndex->nHeight > 44877 && !CheckProofOfWork(GetPoWHash(), nBits))

edit:
scratch that...upon further review all you need is this (cleaner):
change (line 2153 in main):

Code:

    if (fCheckPOW && nHeight > 44877 && !CheckProofOfWork(GetPoWHash(), nBits))

To:

Code:

    if (fCheckPOW && vtx[0].vin[0].scriptSig[0] > 44877 && !CheckProofOfWork(GetPoWHash(), nBits))

And remove the other stuff you added in that function (see above)

hashbros

member

Activity: 104

Merit: 10

Quote from: ReddCoin on March 05, 2014, 11:40:35 PM

Hi everyone,

We are still working on a fix but we need some help. Here is what I posted in the developer forum. It's time to call your C++ professional friends so they can get 1 easy BTC.

While this is happening, nobody will lose their coins as we will start back at block 44877 when we have a fix. We hope to release the final fix in the next 24 hours. We will keep you up to date with the latest development.

Thanks

Reddcoin

Hi

We need some help with Reddcoin. We had a bug in our code, 2 lines were commented so the verification of block we're not done properly.

https://github.com/reddcoin/reddcoin/commit/88fc5fe0bf522e384b7aebfebced12b75e207e80

Someone exploited that error and he was able to grab 7k block in 1 hours. We were able to delete those block but we still need to use the block before 44877, and fix the bug for future block.

What we need to do is this. We need to get nHeight in this function so we can ask the code to check only after block 44877.

in main.cpp, function

bool CBlock::CheckBlock(CValidationState &state, bool fCheckPOW, bool fCheckMerkleRoot) const

I need to get access to the nHeight of the block and that's it to fix the problem.

You can look at our source code to make some test at

https://github.com/reddcoin/reddcoin

1 BTC bounty for anyone who can fix this.

Thanks

Reddcoin

On it!

Topic: [ANN][RDD] Reddcoin The Social Currency [PoSV] Electrum Wallet 1.0.2 - page 104. (Read 688959 times)