Author

Topic: Newly generated coins (Read 1024 times)

legendary
Activity: 4130
Merit: 1307
April 21, 2014, 12:07:53 PM
#14
You are correct. I would put a note like cryptsy to say "Do not mine to this address", only send confirmed coins.

They'd have to be solo mining, not on a pool or going through an exchange.  And I'm sure bitcoind won't show them as spendable, so just check that and you'll be covered in this super duper rare case that will never ever happen.

A few pools send newly mined coins - p2pool for example, although that is the exception.

:-)
cp1
hero member
Activity: 616
Merit: 500
Stop using branwallets
April 21, 2014, 11:56:25 AM
#13
You are correct. I would put a note like cryptsy to say "Do not mine to this address", only send confirmed coins.

They'd have to be solo mining, not on a pool or going through an exchange.  And I'm sure bitcoind won't show them as spendable, so just check that and you'll be covered in this super duper rare case that will never ever happen.
sr. member
Activity: 364
Merit: 250
April 21, 2014, 06:38:49 AM
#12
Thank you for your replies.
Yeah, unless for some strange reason they set you as the coinbase for the mined block you'll be fine.
I agree, that is true for Bitcoin. However, if in the future I would add let's say Crapcoin, the probability someone would set me money as the coinbase becomes higher.

I think I've found a solution to the problem.
If we use listreceivedbyaddress we may txids for each address. Then we use getrawtransaction & decoderawtransaction to determine if it's a newly generated coins.

It there a simpler solution?

New transactions in general are not allowed to be traded if they are newly generated. No coin has changed that yet. So, accept DOGE, LTC, CRAP, whatever, and it will not allow sending newly mined coins.

The problem is, if I understand the process of mining correctly, that someone can set my address as the address to send a POW or POS reward when a new block is mined.

You are correct. I would put a note like cryptsy to say "Do not mine to this address", only send confirmed coins.
sr. member
Activity: 266
Merit: 250
April 21, 2014, 05:28:40 AM
#11
They cant spend them till 100 blocks, unless they were mining using ur address
legendary
Activity: 3472
Merit: 4794
April 20, 2014, 11:52:44 PM
#10
The problem is, if I understand the process of mining correctly, that someone can set my address as the address to send a POW or POS reward when a new block is mined.

And it is easy to determine that has happened.

Make sure that you clearly state with whatever service you are offering that such a payment method is not acceptable.  Then when you receive a payment, verify that it isn't a reward payment.  If it is, treat it as if you haven't been paid yet.  When the customer complains that their payment hasn't been recognized, you can point them to your clearly indicated payment rules, and let them know that once the reward is spendable, you'll refund it to them.
member
Activity: 85
Merit: 10
April 20, 2014, 11:49:05 PM
#9
Let us know when you end building your system to accept bitcoin payments. I'd like to try it and watch how it works Wink
newbie
Activity: 6
Merit: 0
April 20, 2014, 10:12:58 PM
#8
Thank you for your replies.
Yeah, unless for some strange reason they set you as the coinbase for the mined block you'll be fine.
I agree, that is true for Bitcoin. However, if in the future I would add let's say Crapcoin, the probability someone would set me money as the coinbase becomes higher.

I think I've found a solution to the problem.
If we use listreceivedbyaddress we may txids for each address. Then we use getrawtransaction & decoderawtransaction to determine if it's a newly generated coins.

It there a simpler solution?

New transactions in general are not allowed to be traded if they are newly generated. No coin has changed that yet. So, accept DOGE, LTC, CRAP, whatever, and it will not allow sending newly mined coins.

The problem is, if I understand the process of mining correctly, that someone can set my address as the address to send a POW or POS reward when a new block is mined.
sr. member
Activity: 364
Merit: 250
April 20, 2014, 05:58:03 PM
#7
Thank you for your replies.
Yeah, unless for some strange reason they set you as the coinbase for the mined block you'll be fine.
I agree, that is true for Bitcoin. However, if in the future I would add let's say Crapcoin, the probability someone would set me money as the coinbase becomes higher.

I think I've found a solution to the problem.
If we use listreceivedbyaddress we may txids for each address. Then we use getrawtransaction & decoderawtransaction to determine if it's a newly generated coins.

It there a simpler solution?

New transactions in general are not allowed to be traded if they are newly generated. No coin has changed that yet. So, accept DOGE, LTC, CRAP, whatever, and it will not allow sending newly mined coins.
newbie
Activity: 6
Merit: 0
April 20, 2014, 10:13:27 AM
#6
Thank you for your replies.
Yeah, unless for some strange reason they set you as the coinbase for the mined block you'll be fine.
I agree, that is true for Bitcoin. However, if in the future I would add let's say Crapcoin, the probability someone would set me money as the coinbase becomes higher.

I think I've found a solution to the problem.
If we use listreceivedbyaddress we may txids for each address. Then we use getrawtransaction & decoderawtransaction to determine if it's a newly generated coins.

It there a simpler solution?
cp1
hero member
Activity: 616
Merit: 500
Stop using branwallets
April 20, 2014, 12:03:24 AM
#5
Yeah, unless for some strange reason they set you as the coinbase for the mined block you'll be fine.
legendary
Activity: 1628
Merit: 1012
April 19, 2014, 10:25:58 PM
#4
They won't be able to spend them in the first place so they can't pay you with mined coins until they reached the 100 confirmations. Not a problem.

This. They can't get the coins until it reaches the confirmation threshold of the pool, at which point it's a moot point for you to worry about anyway.
newbie
Activity: 26
Merit: 0
April 19, 2014, 10:21:20 PM
#3
They won't be able to spend them in the first place so they can't pay you with mined coins until they reached the 100 confirmations. Not a problem.
hero member
Activity: 672
Merit: 500
April 19, 2014, 07:23:37 PM
#2
100 blocks is only about 17hrs. Can't you add a warning saying newly generated coins may take up to 24hrs to confirm so product dispatch may be delayed.



newbie
Activity: 6
Merit: 0
April 19, 2014, 07:01:46 PM
#1
I'm building my own system to accept bitcoin payments.
I give a new bitcoin address for a customer, wait for him to pay the bill, wait for 1 confirmation (using `listunspent`) and send the customer the product he paid for.
It seems to be the standard way to run things, but I have a question. What if instead of sending the coins from a wallet a customer would send me newly generated coins from a pool? Huh I'll not be able to spend them for 100 blocks. How to decline transactions from the pools (I mean not to return the funds, but not to send the customer the product)?
Or if the money came from a pool, `listunspent` would show confirmations as 0 until 100 new blocks and I just could write "We don't accept generated coins" on my website?
Jump to: