FLOT NSR Operations (buy side)

[masterOfDisaster]

I don’t care who’s in the group (I’m looking forward to work with each of them), but I’d rather have somebody resign than removing someone.

[jooize]

To form the group properly without @dhume and @crypto_coiner the NSR group needs to share 3 members with the NBT group. I can volunteer, but somebody else in @jooize, @ttutdxh and @woodstockmerkle may need to step up.

I can do it at least until more motions pass.

Well, I’m a perfect candidate for leaving since I joined NSR because there were insufficient people available at the time.

[ttutdxh]

I see the value of using a seed now. Wish I had done it from the start.

You can change your pubkey anytime with a proper reason. I expect we will ocassionally have to change individual pubkeys. Certainly, I will.

Múltiple reasons here: new cold storage solution, key compromised, starting to use HD keys, switching to the same seed for all networks like I do…

Edit: also if we use a seed for all of them (NBT, NSR, BTC and in a future PPC) we can create new addresses when needed without waiting for a new public key from each member. Even creating emergency addresses with the certainty of who will be authorized to sign them.

[ttutdxh]

So, @jooize do you volunteer to leave NSR group?

[jooize]

So, @jooize do you volunteer to leave NSR group?

Yes.

[ttutdxh]

Definitive FLOT NSR address T4cQwtThxdh8UWUy5XNPAwPfz73YuZAXqe: wrong @masterOfDisaster pubkey for NSR

Definitive FLOT NSR address SvtGbNjWE49pTM2TiUZrYKSNkxTJx75mmC

(Please check, double check again, and confirm)

[masterOfDisaster]

My pubkey is shown as 02a144af74d018501f03d76ead130433335f969772792ec39ce389c8a234155259 on cointoolkit. (btw - cointoolkit is awesome!)
This is the pubkey of the NBT address I posted here.

The NSR pubkey I posted here in this thread is:
03d05d8fb69fcd289548140dde8e906f6fc217b02477f81842f2483d9ea1c92425 I thought that one would be used for the NSR multisig address

[ttutdxh]

Fixed, I hope so.

[Dhume]

I signed the above NSR address after I verified, no message however appears. Is this correct? Also can we do a test transaction after the multi sig is created?

[ttutdxh]

What did you sign? I don’t follow.

I put 10 NSR into the address, lets make a test.

[Dhume]

No it was my misunderstanding, thought we had to sign to create the address. Let’s do a test transaction!

[ttutdxh]

Sent 2 NSR from FLOT SvtGbNjWE49pTM2TiUZrYKSNkxTJx75mmC to my address SdnvECf6HpfyXjAGuqwGkftWxxsaptBAKP.

FLOT @Dhume, @cryptog, @mhps, @masterOfDisaster lets see if we can all sign this transaction.
0100000037fd58560193c954a714aafbeb04e843ca5cd0efcdc2f8c5b0855ab1dd8bac435e1262f94001000000f800473044022043f8d141140fa8cf8618a3dbc537e65ebb8a176ba89f2e5d69292527a766e64202201db618fdf6637b33c502648fdef5e02903f731430a9ec50e214d86b363aaa53c014cad532102e2fcdfe246e9cd4864d9119b8af465487385eccd0ea30a8cb21d44d36818189f2103661a4370dfcfbcea25d1800057220f4572b6eecab95bb0670e8676a9e34451dc2103686ee42f635c71c08f326e66139b6cb37167402cc0562584655aac03fe74049521039854d0e2abf6e4971e1350137b876da6a05132737c11ca3e37aaed2a0eb668082103d05d8fb69fcd289548140dde8e906f6fc217b02477f81842f2483d9ea1c9242555aeffffffff02701101000000000017a9147077487df91c0166d33ee6079b0c2229788f6ac287204e0000000000001976a914b4fa10acfbc2f6d0920af4c6f33c166d9282b31b88ac0000000053
Transaction already signed by @ttutdxh.

[cryptog]

Apparently I could sign this tx with my private key corresponding to pubkey 03686ee42f635c71c08f326e66139b6cb37167402cc0562584655aac03fe740495 (NSR FLOT) using the Sign Transaction function of cointoolkit that gave me a green result: “Signed transaction
The above transaction has been signed:”

[masterOfDisaster]

The output related tx information seemed appropriate and so I signed it with the private key of my address SXfkA6DgPm6jZZ2RDWAenkUvc1mvVCX42B.
Now it looks like this:
0100000037fd58560193c954a714aafbeb04e843ca5cd0efcdc2f8c5b0855ab1dd8bac435e1262f94001000000fd400100473044022043f8d141140fa8cf8618a3dbc537e65ebb8a176ba89f2e5d69292527a766e64202201db618fdf6637b33c502648fdef5e02903f731430a9ec50e214d86b363aaa53c0147304402204ecf8979769439e68eb65e31ee9b7a59bb3a7e32759de814d84ea42d23ab4adc02202bc39b2c80b98c1f4cf012d886084e1a98067a9ed31a5a13b7bb1725f5cbbf0c014cad532102e2fcdfe246e9cd4864d9119b8af465487385eccd0ea30a8cb21d44d36818189f2103661a4370dfcfbcea25d1800057220f4572b6eecab95bb0670e8676a9e34451dc2103686ee42f635c71c08f326e66139b6cb37167402cc0562584655aac03fe74049521039854d0e2abf6e4971e1350137b876da6a05132737c11ca3e37aaed2a0eb668082103d05d8fb69fcd289548140dde8e906f6fc217b02477f81842f2483d9ea1c9242555aeffffffff02701101000000000017a9147077487df91c0166d33ee6079b0c2229788f6ac287204e0000000000001976a914b4fa10acfbc2f6d0920af4c6f33c166d9282b31b88ac0000000053.

But I have some questions.
How can I verify the txid (40f962125e43ac8bddb15a85b0c5f8c2cdefd05cca43e804ebfbaa14a754c993) or the script of the input (00473044022043f8d141140fa8cf8618a3dbc537e65ebb8a176ba89f2e5d69292527a766e64202201db618fdf6637b33c502648fdef5e02903f731430a9ec50e214d86b363aaa53c014cad532102e2fcdfe246e9cd4864d9119b8af465487385eccd0ea30a8cb21d44d36818189f2103661a4370dfcfbcea25d1800057220f4572b6eecab95bb0670e8676a9e34451dc2103686ee42f635c71c08f326e66139b6cb37167402cc0562584655aac03fe74049521039854d0e2abf6e4971e1350137b876da6a05132737c11ca3e37aaed2a0eb668082103d05d8fb69fcd289548140dde8e906f6fc217b02477f81842f2483d9ea1c9242555ae) easily?
It seems to be different from the one for SvtGbNjWE49pTM2TiUZrYKSNkxTJx75mmC

[mhps]

I think i got it right

0100000037fd58560193c954a714aafbeb04e843ca5cd0efcdc2f8c5b0855ab1dd8bac435e1262f94001000000fd880100473044022043f8d141140fa8cf8618a3dbc537e65ebb8a176ba89f2e5d69292527a766e64202201db618fdf6637b33c502648fdef5e02903f731430a9ec50e214d86b363aaa53c01473044022065cda2fc0015758905dd6ce3de786d46e4bf6cdf5caeb6948f4f79df3fcb561f02206d315f7998baa73e03386b208d82661220d59355930e91e5da5ba72f39fb057a0147304402204ecf8979769439e68eb65e31ee9b7a59bb3a7e32759de814d84ea42d23ab4adc02202bc39b2c80b98c1f4cf012d886084e1a98067a9ed31a5a13b7bb1725f5cbbf0c014cad532102e2fcdfe246e9cd4864d9119b8af465487385eccd0ea30a8cb21d44d36818189f2103661a4370dfcfbcea25d1800057220f4572b6eecab95bb0670e8676a9e34451dc2103686ee42f635c71c08f326e66139b6cb37167402cc0562584655aac03fe74049521039854d0e2abf6e4971e1350137b876da6a05132737c11ca3e37aaed2a0eb668082103d05d8fb69fcd289548140dde8e906f6fc217b02477f81842f2483d9ea1c9242555aeffffffff02701101000000000017a9147077487df91c0166d33ee6079b0c2229788f6ac287204e0000000000001976a914b4fa10acfbc2f6d0920af4c6f33c166d9282b31b88ac0000000053

[ttutdxh]

@masterOfDisaster Right now, you can’t unless you go low level.
That script changes everytime anyone signs, so that is why they are different.
Anyway it will not have any effect if it is wrong, it is not a security problem, the transaction will simply not work.

I have been thinking about a section to do that, and to combine signatures in this scenario:

Member 1 sign the transaction and results in 11a0fff…
Member 2 take 11a0fff… and sign it. He gets 22a0fff…
At the same time member 3 take the same tx signed by member 1, 11a0fff… and sign it himself. He gets 33a0ff…
Now member 2 and member 3 publish their correspondent transactions, 22a0fff, 33a0ff.

Now we have 3 diferent versions of that tx:

• 11a0fff… With signature of member 1. (total 1 of 5)
• 22a0fff… With signature of member 1 and 2. (total 2 of 5)
• 33a0ff… With signature of member 1 and 3. (total 2 of 5)

We don’t have any transactions with the minimum 3 of 5, and we should since 3 of 5 members signed.

---

Only @Dhume, @cryptog left, the transaction from @mhps would already be valid, but lets sign it all to test.

[Dhume]

0100000037fd58560193c954a714aafbeb04e843ca5cd0efcdc2f8c5b0855ab1dd8bac435e1262f94001000000fdd0010047304402205278c55f3a5ccaf7216b2f16a8703463a4b558c7aa9b8ebcb6134afa2e3dacc302202a55e9966081741dad69aba5b037c1e80eccdc1adc0a3f7a70e8e45893d351b701473044022043f8d141140fa8cf8618a3dbc537e65ebb8a176ba89f2e5d69292527a766e64202201db618fdf6637b33c502648fdef5e02903f731430a9ec50e214d86b363aaa53c01473044022065cda2fc0015758905dd6ce3de786d46e4bf6cdf5caeb6948f4f79df3fcb561f02206d315f7998baa73e03386b208d82661220d59355930e91e5da5ba72f39fb057a0147304402204ecf8979769439e68eb65e31ee9b7a59bb3a7e32759de814d84ea42d23ab4adc02202bc39b2c80b98c1f4cf012d886084e1a98067a9ed31a5a13b7bb1725f5cbbf0c014cad532102e2fcdfe246e9cd4864d9119b8af465487385eccd0ea30a8cb21d44d36818189f2103661a4370dfcfbcea25d1800057220f4572b6eecab95bb0670e8676a9e34451dc2103686ee42f635c71c08f326e66139b6cb37167402cc0562584655aac03fe74049521039854d0e2abf6e4971e1350137b876da6a05132737c11ca3e37aaed2a0eb668082103d05d8fb69fcd289548140dde8e906f6fc217b02477f81842f2483d9ea1c9242555aeffffffff02701101000000000017a9147077487df91c0166d33ee6079b0c2229788f6ac287204e0000000000001976a914b4fa10acfbc2f6d0920af4c6f33c166d9282b31b88ac0000000053

[Dhume]

How do we broadcast a valid transaction to the network?

[masterOfDisaster]

Click one of the buttons - the highlighted one
They appear under the signed transaction box after you’ve signed a tx.

I hope it broadcasts the right one. There seems to be a glitch that shares the tx before it was signed and not after it was signed if you click “Verify and share”,
@ttutdxh can you check the “broadcast” function, please?

[ttutdxh]

Let me explain what these buttons do:

• Verify and share: Copies the transaction to the verify tab, you are supposed to check it there, and then you can share the link from “Shareable verification link”. It does not send the transaction anywhere. It is mostly intended to multisig tx.

• Broadcast: It copies the transaction over to the “Broadcast” tab to send it, but it does not send it until you click “Broadcast”. This does not work for most modes because we don’t have servers for that yet, the alternative is “sendrawtransaction [copytransactionhere]” in any wallet debug window.
  However it already works perfectly fine for Bitcoin.