[CLOSED] | 🔥 Coinpayments.net Signature Campaign 🔥 | 100% SegWit |

[babo]

i hope if bitcoin fall down to 2000$ you retouch (increase) value of slot - dynamic reward (in two-way) is fair

I'd argue that even if they don't get changed like that, any changes that are announced before they go into affect (i.e. that they don't affect a on-going period) are fair. However, it doesn't matter for here since it is almost guaranteed that the rates in BTC would spike if the price went down.

Pretty clear, i know you and you are a good signature manager. I write it only for newbie (to avoid further questions)

anyway - advice time - next time is better, in my opinion, create fixed "FIAT" value converted in BTC onfly

I thought about that, but IMO people wouldn't like it. I wouldn't like a fiat based campaign either, but I could run a poll to see what the campaign participants think.

Yep, poll is a good solution.. i hate FIAT, It is a proposal to simplify your life but it's ok in this way

[1715044747]

1715044747

[1715044747]

1715044747

[Lucius]

I think that payment rates look quite decent considering current price of BTC,and that this is the only way to continue this campaign.From the perspective of someone who collects BTC and store it for future lowering pay rates in BTC for sure is not something you want to see,but we can not have high price of BTC in fiat and high pay rates in BTC at the same time.

I am completely satisfied how this campaign is managed, and can only say -  keep up the good work Lauda

[digaran]

Did you see how that beggar regretted his advice? lol. please keep them for some body else, the first week of this campaign 0.0225BTC was $106 and now  is $370. I'm officially *begging on behalf of the begging community, ~Lauda don't create a poll to ask if we'd want a fixed payment in USD or not.


*I didn't ask, I begged.

[leea-1334]

Lauda, I feel that since joining this campaign, I have had one of the smoothest experiences in my short time at bitcointalk. We are always informed, you have been updating ahead of schedule, and we never need to wonder what goes on.

I think we all need to remember that promoting and carrying a signature that pays us is a privilege, not a right. It is enough that we deliver a service and get remuneration as on terms agreed, but it is a bonus that we even can have input, and that it is considered.

All changes fully supported for now and for future, we appreciate very much for openness.

[Lauda]

Thanks everyone, and good news: The campaign is already been funded for January as well (although the funds are not on the same address, and won't be until we need them).

[Lauda]

Payments for Week 11 have been released: https://blockchain.info/tx/2e307a7a0768992c74e5d6f94e8180f53f14cab220b62255406b0bd79f943310.

[Mi5h0]

Payments for Week 11 have been released: https://blockchain.info/tx/2e307a7a0768992c74e5d6f94e8180f53f14cab220b62255406b0bd79f943310.

Thank you Lauda, once again, for your impeccable campaign management and prompt payment. 

[Trofo]

Payments for Week 11 have been released: https://blockchain.info/tx/2e307a7a0768992c74e5d6f94e8180f53f14cab220b62255406b0bd79f943310.

Payment received but still 0 confirmations. Thanks Lauda.

[babo]

Payments for Week 11 have been released: https://blockchain.info/tx/2e307a7a0768992c74e5d6f94e8180f53f14cab220b62255406b0bd79f943310.

Thank you Lauda for payment
And very good news for signature campaign
This happen because you work good

[Lauda]

Payment received but still 0 confirmations.

It will take a while, but both RBF and CPFP are ready.
The campaign is switching to a bi-weekly payment model in order to make our use of block space more efficient (from ~4 KB per month to ~2 KB per month). Everyone who is affected by this has been notified, changes to the thread have been made and changes to the sheet are in progress.

[Searing]

Payment received but still 0 confirmations.

It will take a while, but both RBF and CPFP are ready.
The campaign is switching to a bi-weekly payment model in order to make our use of block space more efficient (from ~4 KB per month to ~2 KB per month). Everyone who is affected by this has been notified, changes to the thread have been made and changes to the sheet are in progress.

No problem. Whatever makes your life a bit easier.

We all appreciate your hard work and the securing of funds for this campaign.....and all the other day to day maintenance and/or issues.

Thanks a lot.

Brad

(hey, no getting hit with a trout this time...progress)

[digaran]

If you need a SW address starting with btc1, don't expect an uneducated beggar to provide you with one, but I will do anything for you.
I created a multisig wallet but only saved xpub and seed, then I created another wallet and provided the xpub of the first one as the cosigner of the second one, this address is from the second wallet, when I want to send funds with it, do I need to open the first wallet? how about segwitaddress.org if I give you an address generated by segwitaddress.org all I'd need is the private key without the need for a cobeggar? can I lol once without getting hit by that already dead trout?

34sKRPi1Wvkrr4W7or8qw3QPdcnxFZi5RF

[Lauda]

(hey, no getting hit with a trout this time...progress)

Damn it..it is so hard to resist..

If you need a SW address starting with btc1, don't expect an uneducated beggar to provide you with one, but I will do anything for you.

That's a bech32 address, or a native SegWit address. A encapsulated P2SH will do fine (i.e. a SegWit address starting with a 3).

I created a multisig wallet but only saved xpub and seed, then I created another wallet and provided the xpub of the first one as the cosigner of the second one, this address is from the second wallet, when I want to send funds with it, do I need to open the first wallet? how about segwitaddress.org if I give you an address generated by segwitaddress.org all I'd need is the private key without the need for a cobeggar? can I lol once without getting hit by that already dead trout?

34sKRPi1Wvkrr4W7or8qw3QPdcnxFZi5RF

You're supposed to hold both keys. I recommend using Electrum (create new wallet using the latest version if you already have one), or Ledger/Trezor to get a SegWit address.

[VitKoyn]

Patiently waiting for the payments to be confirmed.
I think there is no problem if the payout will be changed to bi-weekly, if it will be good for the campaign.
Thank you Lauda for always updating us.

[d5000]

Lauda, I also have no problem with the change. I've already created a Segwit Electrum wallet with Bech32 addresses. If there is no problem sending the coins there (I'm not too familiar with it still), then I'll immediately change the address in my profile to one of these addresses.

Only one question: As far as I understand the PM, this week (until Dec 26) there is still a weekly payout, is this right? (If not, there's no problem with it.)

Thank you for the excellent management of the campaign.

[Trofo]

Only one question: As far as I understand the PM, this week (until Dec 26) there is still a weekly payout, is this right? (If not, there's no problem with it.)

I believe it starts immediately. If you check the spreadsheet you can see the time frame from 19.12.2017. till 02.01.2018.

I am OK with payments every two weeks. I have no clue about segwit addresses for the moment, or what bech32 or encapsulated P2SH means. But no problem I am good at googling things and always willing to learn.

[Lauda]

Lauda, I also have no problem with the change. I've already created a Segwit Electrum wallet with Bech32 addresses. If there is no problem sending the coins there (I'm not too familiar with it still), then I'll immediately change the address in my profile to one of these addresses.

Segwit is fine for now. If you intend on holding, then you can use Bech32. There's nothing wrong with Bech32, other than a lot of services and wallets not recognizing it yet (it has the status draft anyways).

Only one question: As far as I understand the PM, this week (until Dec 26) there is still a weekly payout, is this right? (If not, there's no problem with it.)

No. The next payment is on the 2nd of January. I've mentioned next week in case that someone has a problem with the immediate change; they can thus contact me privately.

[d5000]

Thanks for clarification! I'll look if there is a service I use that doesn't still support bech32, otherwise I'll change the address in my profile.

[digaran]

I can't use an address starting with 3, too complicated for a beggar like me, I don't know as to why would I need to be my own cosigner, when I create a multisig wallet on Electrum, I have no cosigner pub key to provide when it asks me, I only have a seed and a master pub key. since I have no cosigner pub key to insert I would have to cancel the wallet creation process and start over, when I do start over, this time I have the master pub key from the first wallet and I would create a wallet with prefix 3. what happens when I try to spend from that wallet? I would have to open that first half finished wallet with seed and then sign the transaction? what ever I found about this, is a complicated procedure, I don't need to be my cosigner.
I'm officially begging you, don't make me do this, because even if I'd lose the funds, I would provide you an address with a prefix 3. (note that I'm in the process of impressing you, if you are really a girl, (wait, what if I'm not supposed to reveal my plans to you?).

This is a multisig address: 3BPo57Hq42oUGNNVe94ZZaj4gQKywAMghx

Private key: L2uudsa69QYdHH5S8f5TsGzaHJ5Lsrmi9AVYtQwhR3sZoS97xkrQ

How do I spend from it? there is no cosigner here, this was generated with segwitaddress.org could I import the private key and spend? I imported it and it showed a legacy address.

[Decoded]

I can't use an address starting with 3, too complicated for a beggar like me, I don't know as to why would I need to be my own cosigner, when I create a multisig wallet on Electrum, I have no cosigner pub key to provide when it asks me, I only have a seed and a master pub key. since I have no cosigner pub key to insert I would have to cancel the wallet creation process and start over, when I do start over, this time I have the master pub key from the first wallet and I would create a wallet with prefix 3. what happens when I try to spend from that wallet? I would have to open that first half finished wallet with seed and then sign the transaction? what ever I found about this, is a complicated procedure, I don't need to be my cosigner.
I'm officially begging you, don't make me do this, because even if I'd lose the funds, I would provide you an address with a prefix 3. (note that I'm in the process of impressing you, if you are really a girl, (wait, what if I'm not supposed to reveal my plans to you?).

This is a multisig address: 3BPo57Hq42oUGNNVe94ZZaj4gQKywAMghx

Private key: L2uudsa69QYdHH5S8f5TsGzaHJ5Lsrmi9AVYtQwhR3sZoS97xkrQ

How do I spend from it? there is no cosigner here, this was generated with segwitaddress.org could I import the private key and spend? I imported it and it showed a legacy address.

That... is not a multisig address. It's a segwit address. You better not use that address to receive bitcoin, because you just gave your private key away.