[Dev] Develop new core 0.9.3 for feathercoin, together

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…

Bushstar

For SX Txs to be processed you need some miner nodes to be running SX. Really it is dangerous to send SX before the network is updated so SX should not be enabled until a set date in the future.

To test this run two nodes only connected to each other with a couple of empty data dirs so you can mine from the genesis block using the internal miner, or use the testnet. Then you will see if it is confirmed.

Go team!

Between the two of you, Liz and Bush, this should be completely doable it seems right?

lizhi

I plan to build a p2pool on 0.9.3 with Stealth address, hope to confirmed

Bushstar

For SX the entire network needs to be updated for it to be safe.

I will pull and test SX in 0.9.3. It might be sensible to now add your work to the main repo, make sure it is 100% and then release SX and 0.9.3 at the same time.

tmuir12

Cool, but but does this mean no SX before Christmas?

lizhi

I try my best to finish it, But I’m not sure

Wellenreiter

I support Bush’s approach:

merge Bush’s branch on github with Lizhis so we get the hard work from Lizhi ( THANKS LIZHI !!!) into the main trunk
release the 0.9.x version
enable SX several weeks later, when the majority of wallets are updated. The 0.8.7.0/.1 update showed, that it takes a lot of time to get the majority of wallets to the latest version and as Bush says SX is safe only if the whole network is supporting it or at least the majority of wallets/miners

We need a good time table to do it.

Also, what will be the influence on the Android wallet? We already have a backlog and are still short on Android developers who could help here.