I am sorry I don’t follow.
Could you elaborate on that?
I don’t know what happened, but after I read your explanation I tried again and it worked like it should.
What happened on my first attempt: I clicked “Verify and share” and the “Shareable verification link” that was generated pointed to the “old” tx, the one I hadn’t signed. When I recognized that I copied the transaction script from the box and manually replaced it in the “Shareable verification link”.
I tried again just now.
I clicked on @Dhume’s link,
verified the output address and the amount (pretty much all I can/have to verify, right?),
hit the “Continue to Sign” button,
signed it with my privkey,
clicked the “Verify and share” and
recognized that the site that was loaded, contained the proper content (I realized that it showed “Signed: 3” where it previously showed “Signed: 2”).
So there was an error on my end, but I don’t know where.
I’m so happy about this site you created, that it provides the FLOT with an incredibly useful and convenient access to signing transactions!
The cointoolkit can speed up the signing process by orders of magnitude!
If you have your privkeys at hand (safely stored in something like Keepass for Android or iOS), you can sign transactions from your mobile phone!
1 Like
Found why, the input of that transaction is byte-reversed. It shows as 17d4e377a3cab76e028bf8f6b18aeb6c0c8d71777b2aa9722f40c385fbf038e6 and should be e638f0fb85c3402f72a92a7b77718d0c6ceb8ab1f6f88b026eb7caa377e3d417
It was a mistake with the endianness on my end creating the transaction, this new signature should be correct:
010000000117d4e377a3cab76e028bf8f6b18aeb6c0c8d71777b2aa9722f40c385fbf038e600000000fd600100483045022100fe8e34eb8fa0246f9db4a737e2afbf3ea52a29d2bcf2f29d53cf1d5d74d718e5022006513c5959562007fed2054550a254788e412af896a0a2cc42d7ef8de9e8806a014d130155210234139729dd413c84a71a0bfd6f236790be861b37311cef3240277c940e4b0c072102435b894b94b4b27dd24436b3f9ad0b9409d855ab4be6e91141d445804e84750b2102e2fcdfe246e9cd4864d9119b8af465487385eccd0ea30a8cb21d44d36818189f210312cd6eb361c9ebb0d90e44946492a237eab4c7a7d88a0db800f2f460937cc22f21034b0bd0f653d4ac0a2e9e81eb1863bb8e5743f6cb1ea40d845b939c225a1a80ff2103661a4370dfcfbcea25d1800057220f4572b6eecab95bb0670e8676a9e34451dc2103a5fc09a5de595e4758bfbc3a932e2c448cc49a557dd6e64788cee530a76225212103da8082062298c40f0b473b74f3c95b57eaaebe3e67ed30ce56347b2e727915fb58aeffffffff01107a0700000000001976a9142d6ae904b78be00874a1b966dd727944e76957d488ac00000000
@cryptog, @Dhume, @dysconnect, @masterOfDisaster, @jooize, @mhps, @woodstockmerkle, needless to say we need to sign this one again. At least this happened while “testing”, and now we are aware of it.
Just to be on the safe side: I need to check the output address and the amount - nothing else, right?
I’ve asked that before, but I’m not sure whether it was answered.
Here’s the tx signed by me:
Thank you for persistently improving cointoolkit!
And the fee!! (wich currently there is now way of knowing without manually checking the input tx in the blockexplorer or in the wallet command line) Not anymore.
If the sum of the inputs are 100 and the outputs sums 5, 95 goes as fee, and we lose/burn that money. If you calculate the fee for this transaction is 0.0001 BTC.
That should be enough because right now we only have one multisig address, but in the future you may also want to check where that amount is coming from (the input tx) if we have multiple multisig addresses for different purposes.
010000000117d4e377a3cab76e028bf8f6b18aeb6c0c8d71777b2aa9722f40c385fbf038e600000000fd390200483045022100fe8e34eb8fa0246f9db4a737e2afbf3ea52a29d2bcf2f29d53cf1d5d74d718e5022006513c5959562007fed2054550a254788e412af896a0a2cc42d7ef8de9e8806a01473044022036ed83d85da4ea3b04817971649db1df990ccc702ce8852fa6200c5614af38610220346a27374e188c2fb222f9a4de3c51328451e050ffa506ccb572b8e83cc288dd0148304502210085f719446f62ce765a8b84f1690025fd5e367c9363ad774aba43dc065f5c9b9202206c02f4b67584a79658ad822937cb65de5490e795b2364114c2cfb1570c71f26a014730440220204c3ac7e548700b716530c7f1a12b9e55804dadc03483b968fa9192ffe8cc9f0220391e81603355a2d1fca8d69c263a0786851b848a8d70f8c36f4086519651f7d8014d130155210234139729dd413c84a71a0bfd6f236790be861b37311cef3240277c940e4b0c072102435b894b94b4b27dd24436b3f9ad0b9409d855ab4be6e91141d445804e84750b2102e2fcdfe246e9cd4864d9119b8af465487385eccd0ea30a8cb21d44d36818189f210312cd6eb361c9ebb0d90e44946492a237eab4c7a7d88a0db800f2f460937cc22f21034b0bd0f653d4ac0a2e9e81eb1863bb8e5743f6cb1ea40d845b939c225a1a80ff2103661a4370dfcfbcea25d1800057220f4572b6eecab95bb0670e8676a9e34451dc2103a5fc09a5de595e4758bfbc3a932e2c448cc49a557dd6e64788cee530a76225212103da8082062298c40f0b473b74f3c95b57eaaebe3e67ed30ce56347b2e727915fb58aeffffffff01107a0700000000001976a9142d6ae904b78be00874a1b966dd727944e76957d488ac00000000
The above transaction has 4 signers of the required 5.
@jooize @cryptog @dysconnect or @mhps would need to sign
Another thank you and kudos to @ttutdxh for the great work on the toolkit.
010000000117d4e377a3cab76e028bf8f6b18aeb6c0c8d71777b2aa9722f40c385fbf038e600000000fd820200483045022100a664af53c0a24ff02678ed4f85c6eb33c0094ea83e0c87ba8a30622bad11844c02205845be31517b8d7b382544f07cf7ed0eb12716bc8bbf791050f824e2c7a7ab530148304502210085f719446f62ce765a8b84f1690025fd5e367c9363ad774aba43dc065f5c9b9202206c02f4b67584a79658ad822937cb65de5490e795b2364114c2cfb1570c71f26a01473044022036ed83d85da4ea3b04817971649db1df990ccc702ce8852fa6200c5614af38610220346a27374e188c2fb222f9a4de3c51328451e050ffa506ccb572b8e83cc288dd01483045022100fe8e34eb8fa0246f9db4a737e2afbf3ea52a29d2bcf2f29d53cf1d5d74d718e5022006513c5959562007fed2054550a254788e412af896a0a2cc42d7ef8de9e8806a014730440220204c3ac7e548700b716530c7f1a12b9e55804dadc03483b968fa9192ffe8cc9f0220391e81603355a2d1fca8d69c263a0786851b848a8d70f8c36f4086519651f7d8014d130155210234139729dd413c84a71a0bfd6f236790be861b37311cef3240277c940e4b0c072102435b894b94b4b27dd24436b3f9ad0b9409d855ab4be6e91141d445804e84750b2102e2fcdfe246e9cd4864d9119b8af465487385eccd0ea30a8cb21d44d36818189f210312cd6eb361c9ebb0d90e44946492a237eab4c7a7d88a0db800f2f460937cc22f21034b0bd0f653d4ac0a2e9e81eb1863bb8e5743f6cb1ea40d845b939c225a1a80ff2103661a4370dfcfbcea25d1800057220f4572b6eecab95bb0670e8676a9e34451dc2103a5fc09a5de595e4758bfbc3a932e2c448cc49a557dd6e64788cee530a76225212103da8082062298c40f0b473b74f3c95b57eaaebe3e67ed30ce56347b2e727915fb58aeffffffff01107a0700000000001976a9142d6ae904b78be00874a1b966dd727944e76957d488ac00000000
It seems that the tx went through, which implies that the necessary number of signatures has been reached.
I will sign the tx just for fun later on and for training purposes.
EDIT: signed the tx after it has been broadcast to increase the number of signers from 5 to 6 though the necessary number is 5.
Got the following signed tx:
010000000117d4e377a3cab76e028bf8f6b18aeb6c0c8d71777b2aa9722f40c385fbf038e600000000fdca0200483045022100a664af53c0a24ff02678ed4f85c6eb33c0094ea83e0c87ba8a30622bad11844c02205845be31517b8d7b382544f07cf7ed0eb12716bc8bbf791050f824e2c7a7ab530148304502210085f719446f62ce765a8b84f1690025fd5e367c9363ad774aba43dc065f5c9b9202206c02f4b67584a79658ad822937cb65de5490e795b2364114c2cfb1570c71f26a01473044022036ed83d85da4ea3b04817971649db1df990ccc702ce8852fa6200c5614af38610220346a27374e188c2fb222f9a4de3c51328451e050ffa506ccb572b8e83cc288dd01483045022100fe8e34eb8fa0246f9db4a737e2afbf3ea52a29d2bcf2f29d53cf1d5d74d718e5022006513c5959562007fed2054550a254788e412af896a0a2cc42d7ef8de9e8806a014730440220204c3ac7e548700b716530c7f1a12b9e55804dadc03483b968fa9192ffe8cc9f0220391e81603355a2d1fca8d69c263a0786851b848a8d70f8c36f4086519651f7d80147304402205bc28c504ce0d2632c04869b87fc4da0eac580815c0a481344cd00bd9fb8767602207788d08559455b60e993ef7af173351dabf7304910a1a555a21e78cc4b92a65f014d130155210234139729dd413c84a71a0bfd6f236790be861b37311cef3240277c940e4b0c072102435b894b94b4b27dd24436b3f9ad0b9409d855ab4be6e91141d445804e84750b2102e2fcdfe246e9cd4864d9119b8af465487385eccd0ea30a8cb21d44d36818189f210312cd6eb361c9ebb0d90e44946492a237eab4c7a7d88a0db800f2f460937cc22f21034b0bd0f653d4ac0a2e9e81eb1863bb8e5743f6cb1ea40d845b939c225a1a80ff2103661a4370dfcfbcea25d1800057220f4572b6eecab95bb0670e8676a9e34451dc2103a5fc09a5de595e4758bfbc3a932e2c448cc49a557dd6e64788cee530a76225212103da8082062298c40f0b473b74f3c95b57eaaebe3e67ed30ce56347b2e727915fb58aeffffffff01107a0700000000001976a9142d6ae904b78be00874a1b966dd727944e76957d488ac00000000
I see three confirmations in 2 hours
The deadline for December payment for JordanLee uncompetitive fee of double each month is on 1 of December.
So I formally ask that half of the T4 funds in @JordanLee control are transferred to FLOT controlled address 3QDWJ2yqJ5iTUg6cSpAwxx95ba3NG97hzG
5 Likes
Fine with me.
After all that’s what the FLOT is here for and I think it’s in the position to do that.
I think he said something to the effect that when FLOT actually forms he’ll cut some slack in his fee, but I couldn’t find the post.
I also thought so, but couldn’t find it either. Maybe we wanted to believe that.
So how much do you ask to be transferred to FLOT? We need to be at least half
Strange coincidence - I remembered the same, but didn’t find anything related from Jordan when searching after “fee” or “compensation”.
Maybe @JordanLee can shed some light on this.