[Dev] Develop new core 0.9.3 for feathercoin, together

wrapper

More info on the Litecoin Multisig “bug” on Github. First ever Litecoin hard fork…

Re: Need to make sure FTC multisig addrresses also is not start with 3…

I agree it has been a problem. #blamecoblee =P The unfortunate problem with this type of transition is that it would require the first ever hardfork in Litecoin’s history. Can the plan be written in a more detailed proposal in the format of a Bitcoin BIP? We will need to propose it to the community, receive feedback and buy-in from stakeholders.

lizhi

Yes, I find FTC multisig addrresses also is start with 3…

The unfortunate problem :'(

It is not a bug, However, it is easy to make us confused ;)

A back in github

“I think you can contact Quickwallet (https://twitter.com/quickwalletcom), they are huobi store’s website, is to use Multisig addresses versions are ‘3’.”

We can not modify rpcmisc.cpp.

Wellenreiter

I got the 0.9.3 core compiled on OpenSuSe 12.3

It was a bit tricky, as OpenSuSe uses non-standard directories for 64bit libraries and the dependencies are always a challenge ;)

Good Work Lizhi!

I noticed that I can’t create qr-codes in the ‘receive’ tab,although I configured with --enable-qr=yes

lizhi

I think we need to support qr-codes ,I will read 0.8.7 codes , then find them.

wrapper

Re: Multisig prefix, same for Bitcoin, LTC and FTC.

I note Charlie is proposing multiple start values for LTC, al la Ghostlanders solution for the genesis code confusion between coins.


I think changing Litecoin multisig prefix is a good idea. Anton, are you suggesting doing this as a soft fork? Basically, we can have it so that new versions allow both '3' and '4' addresses. '4' addresses will be rejected by the network until the soft fork happens. If you can write up a detailed proposal, that would be helpful.

â€"  
Reply to this email directly or [view it on GitHub][0].![AEZWALX8V_a1kKgRA9QMZPR0z15v83pJks5nNGjf](https://github.com/notifications/beacon/AEZWALX8V_a1kKgRA9QMZPR0z15v83pJks5nNGjfgaJpZM4C3HPH.gif)

I realise that this would need its own development sub area. But this will cause a lot of problems to exchanges and merchants accepting multicoins, so would be a killer feature (over Litecoin) and may not require a hard fork if it is developed before release. Although I haven’t had time yet to fully investigate the details of the development of multisignature technology.

kris_davison

so how difficult would it be to change our multi sig address to something other than 3/4 e.g. 9 or whatever.??

lizhi

Now, Core Wallet support QRcode, I will continue to complete QR-snap.

tmuir12

Wow, you have been busy, would be great to get this made the official wallet soon

lizhi

so how difficult would it be to change our multi sig address to something other than 3/4 e.g. 9 or whatever.??

I think changing Feathercoin multisig prefix is a good idea, But I need helpful.a detailed proposal.

lizhi

I solved the issue, Core wallet can support QR-Snap .

I must modify ZebraCrossing, Because it compile on Visual Studio 2013 only.

How to compile ZebraCrossing

 cd /D/FTC/dev/ZebraCrossing-master
 mkdir mw
 cd mw
 cmake -G "Unix Makefiles" ..
 make

then libzxing.a copy *.a to /D/FTC/dev/ZebraCrossing-master/build32/Release

You need to modify some files

BitMatrixParser.h and DecodedBitStreamParser.cpp, create a new stdint2.h

typedef long int int64_t;

LinesSampler.cpp

add #include

delete using std::abs;

I had add USE_ZXING option to configure.ac , A simple way is to directly modify src\qt\Makefile.

CPPFLAGS = -I/D/FTC/dev/ZebraCrossing-master/src/libsrc
LDFLAGS = -L/D/FTC/dev/ZebraCrossing-master/build32/Release
LIBS = -lzxing -L/D/FTC/dev/ZebraCrossing-master/build32/Release

Wellenreiter

is that on your github?

Then I could try to compile on Linux

MrWyrm

Woo!

lizhi

is that on your github?

Then I could try to compile on Linux

Yes, I had git my codes . https://github.com/cqtenq/feathercoin_core

Bush’s ZebraCrossing lib https://docs.google.com/file/d/0B3j45cVgrEz0Qkg2bndIWENBMDg/edit

**libzxing ** https://github.com/ClaireDuSoleil/ZebraCrossing

Any questions please let me know.

So how do we go about getting this new core fleshed out and implemented as the defult core?

I assume there’s still a lot of testing required?

lizhi

I assume there’s still a lot of testing required?

Yes, I think so. Multisig need to optimize. All of the code need to be carefully tested.

I need a month’s time at least, Testing, comparison, modification, optimization, learning, that sort of thing .

Now it is a Alpha 2.

Feathercoin Core 0.9.3 QT-Wallet Downloads (binary for windows Alpha 2)
https://forum.feathercoin.com/index.php?/topic/8018-friendly-testneed-volunteers-feathercoin-core-093-alpha-released/

I’ll assume that is the new Primary thread, so ive moved, pinned, unpinned things around. Dev/testing stuff was seeping into the discussion area.

lizhi

You give me infinite power , developed the new multisign address, prefix f. ^-^

https://forum.feathercoin.com/index.php?/topic/8113-dev-multisignature-wallet-implementation-and-issues/#entry70825

lizhi

ABout Stealth Address, I had add some codes to test, Now I can create a stealth address for feathercoin, but some issues need to fixed.

lizhi

I can create a transaction with stealth address, then Commit the transaction , The transaction has already been signed and recorded. final Broadcast it .

Issue

Can not confirm the transaction on feathercoin main_net :- ???

Stealth address= dooJagc2DuuHdKmkRDvgVrFwwxQKYXeGR3Pqsi1yqhtw5LgMToZvEYsX4rjubvSQi63s8xWRFnFLDSnmDW5f2B8QGXNnbbxReWSGrZ

Real feathercoin address=6qSmao2FFTyw4QCDJsP4WYSVejb5vjfinj

transaction id=4fd68296fb09e79be18f9936fa5d9a7c135fa6ebb6d79f6ad85bb3f36c5878be

Debug.log: (CWallet::CommitTransaction in wallet.cpp)

2014-12-08 07:57:16 CommitTransaction start…
2014-12-08 07:57:16 CommitTransaction:
CTransaction(hash=4fd68296fb, ver=1, vin.size=1, vout.size=3, nLockTime=0)
CTxIn(COutPoint(b0392d9512, 0), scriptSig=3045022100e5d3f21ed892de)
CTxOut(nValue=0.13000000, scriptPubKey=OP_DUP OP_HASH160 bb1b7589bec3)
CTxOut(nValue=0.00000000, scriptPubKey=OP_RETURN 02821fd33b110e92e73d)
CTxOut(nValue=0.06418968, scriptPubKey=OP_DUP OP_HASH160 cb7bd98df210)
2014-12-08 07:57:16 keypool keep 50
2014-12-08 07:57:16 AddToWallet 4fd68296fb09e79be18f9936fa5d9a7c135fa6ebb6d79f6ad85bb3f36c5878be new
2014-12-08 07:57:16 CommitTransaction Broadcast start…
2014-12-08 07:57:16 AddToWallet 4fd68296fb09e79be18f9936fa5d9a7c135fa6ebb6d79f6ad85bb3f36c5878be
2014-12-08 07:57:16 Relaying wtx 4fd68296fb09e79be18f9936fa5d9a7c135fa6ebb6d79f6ad85bb3f36c5878be
2014-12-08 07:57:16 CommitTransaction RelayWalletTransaction…