Bitcoin Forum

Bitcoin => Bitcoin Discussion => Topic started by: hotcoin010309 on June 21, 2016, 10:45:39 AM



Title: Block size and the time required for the transaction can stop pump&dump BTC?
Post by: hotcoin010309 on June 21, 2016, 10:45:39 AM
Hi guys

Actual block size and the time required for the transaction can stop the speculation on bitcoin?

If want move big size of bitcoin, transaction is very long time, right?

How can move a big quantity of btc for dump? Now is complicated...

This  phenomenon can stop (or limit) pump&dump effect?

What do you thinks?

il tempo necessario per transazione


Title: Re: Block size and the time required for the transaction can stop pump&dump BTC?
Post by: Kakmakr on June 21, 2016, 11:25:18 AM
Well, if a lot of people are doing loads of small transactions, they might be halted temporarily to proceed, if the blocks are full, but this will have to be a well timed event from a lot of people. The dumping of coins can happen with one single transaction, so block sizes will have no influence on that. ^hmmm^


Title: Re: Block size and the time required for the transaction can stop pump&dump BTC?
Post by: hotcoin010309 on June 21, 2016, 11:58:14 AM
Ok, but how many transaction for transfer a qty necessary for "dump"?? If i want sell 500-1000 btc (volume min for rise or down price)i must first move from my wallet to exchange....
500 btc how many time need for complete transaction( whole o partial )?


Title: Re: Block size and the time required for the transaction can stop pump&dump BTC?
Post by: DannyHamilton on June 21, 2016, 12:09:37 PM
Hi guys

Actual block size and the time required for the transaction can stop the speculation on bitcoin?

Nope.  Complete nonsense.

If want move big size of bitcoin, transaction is very long time, right?

Nope.  Complete nonsense.

How can move a big quantity of btc for dump? Now is complicated...

Nope.  Complete nonsense.

This  phenomenon can stop (or limit) pump&dump effect?

Nope.  Complete nonsense.

What do you thinks?

I think that's a whole lot of nonsense.

Ok, but how many transaction for transfer a qty necessary for "dump"??

One transaction.

If i want sell 500-1000 btc (volume min for rise or down price)i must first move from my wallet to exchange....

Correct.

500 btc how many time need for complete transaction( whole o partial )?

Same as always.  10 minutes on average per confirmation, and the required number of confirmations is determined by the exchange service.


Title: Re: Block size and the time required for the transaction can stop pump&dump BTC?
Post by: hotcoin010309 on June 21, 2016, 01:00:45 PM
Hi guys

Actual block size and the time required for the transaction can stop the speculation on bitcoin?

Nope.  Complete nonsense.

If want move big size of bitcoin, transaction is very long time, right?

Nope.  Complete nonsense.

How can move a big quantity of btc for dump? Now is complicated...

Nope.  Complete nonsense.

This  phenomenon can stop (or limit) pump&dump effect?

Nope.  Complete nonsense.

What do you thinks?

I think that's a whole lot of nonsense.

Ok, but how many transaction for transfer a qty necessary for "dump"??

One transaction.

If i want sell 500-1000 btc (volume min for rise or down price)i must first move from my wallet to exchange....

Correct.

500 btc how many time need for complete transaction( whole o partial )?

Same as always.  10 minutes on average per confirmation, and the required number of confirmations is determined by the exchange service.






Four days ago,  moved , from my portfolio to 2.2 btc bitsmap the transaction is more than 18 hours duration ...


Only in a transaction it is impossible to sell 500 btc, bid on, there must be a proposal for purchase of 500btc or more to run in a single transaction.

Multi-transaction can be executed


How many bitcoins have moved at best your experience with it?


Title: Re: Block size and the time required for the transaction can stop pump&dump BTC?
Post by: hotcoin010309 on June 21, 2016, 01:03:03 PM
this in one example: 2e7e3f1fb228f539a2de3a68beaa66ade6b277e30fa40c927599d14d30f2f2ab