Topic: [BOUNTY] 0.025 BTC (or 2500 CRDS) to find bug with multsig payments (Read 325 times)
A very good project.
March 10, 2018, 03:41:20 PM
I think I found and fixed the bug.
I'm leaving this here as a kind of timestamp of when I had what I think it is:
I'll publish the file once I've spoken with the devs.
I'm leaving this here as a kind of timestamp of when I had what I think it is:
$ shasum -a 512 fix.txt
0d9d7753257c96ab50565a4d542cf41bc37c2815a6a83ada04d03c2ba7469eca1edad18f46fd6c0 8b4c4f6b945517e369d84ce787162c5087106455729e3ce08 fix.txt
I'll publish the file once I've spoken with the devs.
March 09, 2018, 12:36:45 AM
saw that one? https://bitcointalksearch.org/topic/m.31684304
Yes he didn't fix anything, he was just able to produce a multisig address which is not an issue. I have let him know this on Discord. March 08, 2018, 09:08:04 PM
saw that one? https://bitcointalksearch.org/topic/m.31684304
March 06, 2018, 10:35:12 PM
We are offering either 0.025 BTC or 2,500 CRDS (your choice) to whomever can identify what in our code is causing this issue.
The latest release can be found at https://github.com/CRDS/Credits/releases
The issue may be to do with the actual multisig addresses themselves or to do with the handling of fees when sending CRDS to the multisig address. Not that CRDS was created as a fork of DYN v1.4 and DYN's multisig was and is still working perfectly.
I'm happy to provide those wanting to work on this with 1 CRDS to test with, just DM me (Matt Rankin) on Discord - https://discord.gg/DjSfNtp
Jump to: