If I select all my unspent inputs transaction size would be ~11474 bytes. Tooltip says that with transaction sizes over 10000 bytes tx fee will
be at least 0.01 YAC per kB but fee shown on CC window is 0.01 YAC at all times, no matter if I select just one unspent input or all of them. By
default, no fee is added to transactions (Settings > Options > tab Main). All unspent inputs are 440 YAC at least and have high priority. Since
I'm still waiting for PoS to generate, I can't tell what final tx fee I'm supposed to pay, e.g. if tx fee for sending all inputs would be 0.11+ YACs.
Transaction fee shown at CC window is indeed stucked at 0.01 YAC, e.g. it is not calculated properly. I just picked large number of inputs, sent coins and actual fee was 0.05 YAC but CC window reported just 0.01 YAC. Normal CC operations (selecting inputs, receive and change addresses and so on) seem to be working fine. All coins "landed" where they should. Thanks for the feedback! I'll look into the fee issue. |
|
|
|
I cloned the latest revision of WindMaster's git repo, so it's up-to-date. Will build x64 with UPnP and QR in a while.
Add in the checkpoint at 165,000 (I pushed it to my GitHub repo yesterday) sometime when you're already in there editing: ( 165000, uint256("0x00000001e790d65de9541af419465338220de69e3ffcbda427af2fc94741d321")) After more testing has happened, I'd welcome a pull request of your coin control changes back to my repo. Good work on implementing this! Fetched and cherry-picked. @ sairon and shakezula
Does your builds include latest checkpoints, e.g. latest WindMaster's code? Also, it seems sairon Win version is 64 bit but shakezula uPnP version is
Win 32 bit, could we have uPnP enabled Win 64 bit version as well? I'm personaly using 32 bit version but community might be more into 64 version.
So apparently my build is also 32-bit. -.-" I hate Windows so much... Will try building a proper 64-bit version with both UPnP and QR support soon TM. |
|
|
|
Since you already have the adresses listed it would be useful feature to optout singe adresses for PoS.
Since you are in control of inputs to be used for transactions there is no need to reserve balance or whatever, just do not use inputs you want to be used for stake generation. If all such inputs are on the same address than name address STAKE DO NOT TOUCH or something and that's it. I meant someting different: If I don't want an adress to be used on PoS I can't (easily) prevent that from happening. I don't want my spare change adress to generate PoS and there might be situations where you want to have some funds aviable. That's what the input locking is for in the most recent release of Bitcoin-Qt. |
|
|
|
@ sairon and shakezula
Does your builds include latest checkpoints, e.g. latest WindMaster's code? Also, it seems sairon Win version is 64 bit but shakezula uPnP version is
Win 32 bit, could we have uPnP enabled Win 64 bit version as well? I'm personaly using 32 bit version but community might be more into 64 version.
I cloned the latest revision of WindMaster's git repo, so it's up-to-date. Will build x64 with UPnP and QR in a while. |
|
|
|
Could you tell us a bit more about your implementation, and if you'll be able to keep up with any eventual future changes to Coin Control and YACoin client?
As for the implementation: I took all the code from this pull request by cozz https://github.com/bitcoin/bitcoin/pull/2343, changed a few things so that it would be compatible with YaCoin (which is based on NovaCoin which is based on older version of Bitcoin lacking some new features like input locking and whatnot). I'm not entirely sure if I got all of it right, especially the transaction fee computation part, but hopefully it's OK (and it's just a cosmetic issue, the client will compute the neccessary fee itself). I'm also happy to add any new features that cozz might release in the future (or YaCoin client changes, but that might not be an issue if we merge this into the "official" client). Anyway, is WindMaster around? We need him to update official unofficial YACoin GitHub, if your Coin Control version passes tests. Given that CC
is optional and does not affect "classic" client at all unless user decides to use CC, there is no good reason to maintain two GitHubs or whatever.
Yes, it's optional as in the original Bitcoin version by cozz. You don't see anything until you turn it on in the options. I'll wait until there are some positive responses to this build and then open a pull request in WindMaster's repo if that's what the YAC community wants. |
|
|
|
I am offering this bounty to anyone who can solve this problem for me...
When I send YaCoins from my wallet, I do not know the coin age of the coins that are included in the transfer, so I want certain features built into my wallet (I have WINDOWS 64 btw):
-tracks coins in the wallet according to their respective coin age
-allows the ability to discern which coins (defined by coin age) to send when making a transaction
-[USER FRIENDLY--a term lost to many crypto junkies] I need to be able to do previous mentioned items without typing commands in a console
I have never offered a 'bounty' previous, so if there is something else I need to do, let me know.
I have already offered 1 BTC reward for such feature, which is called Coin Control. Once you start using it, you'll never want to go back! I'll send you my bounty reward as soon as I test the client in-depth and find it working properly, it might take some time though. Nice to see so many people that want this feature.  |
|
|
|
|
Is someone using this? Need some testers, c'mon!
Lemme know if you need UPnP support compiled into the client, didn't do it 'cause it was a major hassle already under Windoze.
|
|
|
|
================================ EDIT: NEW UPDATE 2013-12-09:
New windows binaries released, updating requires user intervention!You NEED to move/rename (backup) everything except wallet.dat and peers.dat in the yacoin data directory and then run yacoin with -loadblock=C:\blk0001.dat (assuming you put the blk0001.dat file in C:\). This is needed because we had to change the way blocks are indexed and now the wallet starts in LESS THAN 30 SECONDS (down from more than 30 minutes). However, this initial load will take somewhere around 2 hours (still faster than downloading it through the p2p network). If you don't mind redownloading all the blocks, you can just remove the unneeded files and start yacoin normally (less hassle, but takes more time). Most of the time at startup is now spend verifying the last couple of blocks (which needs to to recompute their hashes to ensure integrity). I've lowered this number from the default 2500 to 666 (rather arbitrarily chosen, but should absolutely be set higher than 520). ================================ Announcing YaCoin-Qt client with Coin Control features!YaCoin - The FIRST AltCoin with Coin Control!Do you wanna: - send specific Unspent Outputs but the Qt client keeps choosing them randomly?
- have control over your Anonymity? (Well, pseudonymity, to be precise.)
- have control over your Coin Age?
- maximize your Proof of Stake rewards?
- choose the Change Address yourself?
- know the Transaction Fees associated with your transaction before attempting to send it?
- see the Transaction Priority of your transaction?
Then Coin Control is just the thing for you! NOTE: Enable in Settings -> Options -> Display, check "Display coin control features (experts only!)". Aaaand it's done. Enjoy. Disclaimer: Don't download anything if you don't trust me. Do your homework. Review the github repo code commits. Compile it yourself. Compiling for Linux:git clone https://github.com/saironiq/yacoin-cc.git
cd yacoin-cc/src
make -f makefile.unix
cd ..
qmake
make
(with some minor variations) Donations welcome! Some screenshot pr0n:  |
|
|
|
Great, I will look into later. Maybe someone else can as well? From what I understand Coin Control has nothing to do with 'coin age' as coin control is for managing multiple addresses and was originally built for Bitcoin--obviously coin age does not apply, no Proof of Stake.
When you switch to list view, you'll see the exact date/time of all all your outputs. From there you can derive input age. |
|
|
|
|
I'll also post this here:
yacoin-cc-qt.zip (8.1 MB)
(link removed as it contained a critical bug)
|
|
|
|
Does it satisfy all requirements?
I guess so. Give it a try and lemme know if something's not right. I don't have LINUX... I have Windows 64 OK, I've built it for you (although compiling under windoze is a royal PITA -.-"). Just unzip and it should work. yacoin-cc-qt.zip (8.1 MB) (link removed as it cointained a critical bug) |
|
|
|
I can't find it, but I am very sure I read such a post. ~1 Month ago... Yeah, I saw it, too. That's what made me thinking about implementing it in YAC. And those new bounties just made me do it faster.  |
|
|
|
Does it satisfy all requirements?
I guess so. Give it a try and lemme know if something's not right. |
|
|
|
Guess I'll have to release it in order to get some testing going.  So here comes... YaCoin Wallet with Coin Control!Git repo: https://github.com/saironiq/yacoin-ccCompile as usual, eg. for linux: git clone https://github.com/saironiq/yacoin-cc.git
cd yacoin-cc/src
make -f makefile.unix
cd ..
qmake
make
Then in Settings -> Options -> Display, check "Display coin control features (experts only!)". Aaaand it's done. Enjoy.   |
|
|
|
I'm working on porting Coin Control into Yacoin-QT client. All bounties welcome Great, I'm really looking forward to this. The compile finished successfully, so it should work.
Shit. Couldn't you have written that a little bit earlier and saved me some yacs? I tought someone might be already working on that but why didn't I trust my instincts ... Just for curiousity, wouldn't you have announced your update to Yacoin-qt today anyways? Haha, sorry for that. Sure I would announce it, why not? Are you interested in testing it? You'll have to compile it from source yourself, tho... |
|
|
|
There was a similar high bounty for making Coin Control compatible with Yacoin.
Where is that? I think we need an official YAC bounty threat first. There is one at https://bitcointalk.org/index.php?topic=200311.120, but it seems not in use much... I will offer a 25,000 YaCoin bounty for anyone to make this feature if it is even possible...
In this threat that might get lost, so if you serious about that start a new threat so more people find it. I'd also add 5k to it, but at first we have to bundle all bounties for CC to see how much is actually on it. Maybe it would be a good idea to also put up the bounty in BTC to attract programmers outside of altcoins... I'm working on porting Coin Control into Yacoin-QT client. All bounties welcome EDIT: The compile finished successfully, so it should work. Need some testers! Anyone interested? |
|
|
|
|
Show Posts
