[Dev] Release Candidate Feathercoin 0.9.3.2 - Check List

[wrapper]

Hopefully it’s something like that. I thought I’d pulled any changes, I’ll let you know.

Explicitly use boost overloaded functions in base58 vector ?

[Wellenreiter]

regarding bitmessage:

exec python /home/USER/programs/PyBitmessage/src/bitmessagemain.py  bitmessagemain.py

should be

cd   /home/USER/programs/PyBitmessage/src
exec python bitmessagemain.py

assuming that bitmessagemain.py and the other .py files are in the directory /home/USER/programs/PyBitmessage/src

[wrapper]

@Wellenreiter I’ve done a git pull, It looks like I was up to date.

I will test a resync from the failed test with a rebuild

then if it still fails :
try a rebuild from scratch and see if it fails at the same place.

[wrapper]

Re:

Hurrahhh !!! !!!

[wrapper]

If we change the script can we send the message to Telegram (or such) instead?

A medium term fix would be to detect the BitMessage status and set the script or .bat file as part of the install.

The long term aim would be to make the plugins, at least, to have options check boxes to include on the menu.
A generic system where you can include additional plugins to run a script

[wrapper]

@Wellenreiter

cd   /home/USER/programs/PyBitmessage/src
exec python bitmessagemain.py

assuming that bitmessagemain.py and the other .py files are in the directory /home/USER/programs/PyBitmessage/src

That isn’t working on drop down test to pass anything through to Bitmessage, I think we need to create a pass through variable? probably text.

[wrapper]

I tried this in the script :

exec python bitmessagemain.py $1

Transaction Grid Right Click - that didn’t work for me. the right click doesn’t open BitMessage either.

[lizhi]

Great work wrapper, Can you push your codes and images to github ?

[wrapper]

@Lizhi : All the new Icons and dev changes are on on http://github.com/wrapperband/Feathercoin.git

AFB is having a look at the splash screen, we have just found how to make the animation movie, by using the make_spinner.py python script in Feathercoin/share/qt to make the png spinner files .

We are looking at what the windows script make_windows_icon.sh in the same directory, to see if that needs regenerating before the final beta test version.

When Wellenreiter is ready we will pull them into FTC version.

Sync issues : Possibly missing Patch - Re Testing Re-Synchronisation from install : Passed + very fast.

[wrapper]

Thanks to AFB, here’s the new splashscreen in action …

[AcidD]

when is AFB gonna get an account so we can start giving Kudos ?! Great work!

[wrapper]

AFB has been a forum member since 2013.
Were trying to optomise any time we have with development, so I’ve done all the posting and Githubs for AFB so far. I’ve asked him to do a post, but we’ve had quite a lot to learn and do which would be, “quite daunting to anyone with any sense!”

[wrapper]

Test : Exporting and Importing a URI
Status : Failed

Can someone double check I am not doing something wrong. Se-up VirtualManager start FTC -> copy URI of recieve address, import that into FTC. Nothing happens.

I could not paste a URI or open a text imported from a URI file.

There was no way to save the URI file on the QRCode / Address creation pop up (only copy to clipboard).

[wrapper]

The level of dust payment / minimum transaction level fee is ridiculously high 1% this seems to be for historical “reasons”, like encouraging high value transactions.

So, for instance, what is the point of having mFTC and uFTC when they pay 1000% fee?

I propose min fee is moved to 0.001 FTC,

The main problem with this is mFTC has 100%fee, when smart contracts come in they might be under priced :

We can enforce a higher fee for smart contracts, i.e they will have 2 parts,
rejestering the contract - 0.01 min : pay a extra fee to speed up.
running the contract : pay a contract fee 0.01 min - pay extra to speed up

http://bitcoin.stackexchange.com/questions/24869/1-500-transaction-fee-and-3-5-months-to-confirm

[lizhi]

wapper , your GUI is OK , I jump our version to 0.9.3.3

download URL http://www.ftc-c.com/pack4/feathercoin-setup-0.9.3.3.exe

[wrapper]

@lizhi

Thanks Lizhi. I was hoping to give Wellenreiter a chance to do a double check or the code. So I hope you find the “deliberate mistakes” we put in so it doesn’t get released untill 0.9.6 !

Seriously, I will pull 0.9.3.3 into my development area.

I am very tired at the moment and AFB is busy we still are working on a couple of things.

I also also still require some better screen shots for Your Multisignature demo in the Feathercoin Wallet Guide .

I still need convincing there are not issues with- signing varying, and importing URLs as I was get them to work with my version.

We need somone to go through every option in the windows version and check the UI works and Text is correct in other languages, that each feature works. I will send a couple of test FTCs to anyone who’ll try that.

NOTE : 0.9.33 is not to be used for MINING…

[wrapper]

Updated the Title to 0.9.6

[Wellenreiter]

@wrapper said in [Dev] Release Candidate Feathercoin 0.9.3.2 - Check List:

The level of dust payment / minimum transaction level fee is ridiculously high 1% this seems to be for historical “reasons”, like encouraging high value transactions.

So, for instance, what is the point of having mFTC and uFTC when they pay 1000% fee?

I propose min fee is moved to 0.001 FTC,

The main problem with this is mFTC has 100%fee, when smart contracts come in they might be under priced :

We can enforce a higher fee for smart contracts, i.e they will have 2 parts,
rejestering the contract - 0.01 min : pay a extra fee to speed up.
running the contract : pay a contract fee 0.01 min - pay extra to speed up

http://bitcoin.stackexchange.com/questions/24869/1-500-transaction-fee-and-3-5-months-to-confirm

The transaction fee is payed to the miners finding a block. The idea behind it is, that after all coins habe been mined, we still need to give miners an intensive to mine, and that there will be a sufficient number of transactions per block, so that the cost of mining is covered.
If we lower the fee, we mFTC and µFtC transactions are not overpaid, but we may face problems with a constantly low hashrate.

[wrapper]

This post is deleted!