Author

Topic: Wall Observer BTC/USD - Bitcoin price movement tracking & discussion - page 19150. (Read 26706935 times)

hero member
Activity: 674
Merit: 500
Daily reminder that ETH was disgustingly pre-mined by dishonest ETH devs and will soon be mega-dumped causing Ethereum to plummet.

There is a ton of shills shilling for this shitcoin on various websites but I guarantee you, I've seen shitcoins come and go, this is no exception.

No one will be talking about Ethereum in a month or two because dishonest devs and whales will cash out and laugh their way to the bank.

In three months another shitcoin will arise and shills will shill that shitty shitcoin.

Meanwhile bitcoin will continue to be the only crypto coin worth holding, now and forever.


-------------------------------------------------------------------------------

In other news the jewish-controlled mass media attempted to stump the Trump with this "KKK" nonsense but the God Emperor remains unstumped on his way to the white house in 2017.

Oklahoma, Texas, and Minnesota are confirmed cucks but the God Emperor took the majority of states this Super Tuesday.

We won't have a spic cuban, we won't have a cunt, and we're not going to have a commie president in 2017.

The God Emperor is the only choice.

MAKE AMERICA GREAT AGAIN

Donald Trump for President!

legendary
Activity: 2380
Merit: 1823
1CBuddyxy4FerT3hzMmi1Jz48ESzRw1ZzZ
legendary
Activity: 2380
Merit: 1823
1CBuddyxy4FerT3hzMmi1Jz48ESzRw1ZzZ
legendary
Activity: 1260
Merit: 1116
legendary
Activity: 2380
Merit: 1823
1CBuddyxy4FerT3hzMmi1Jz48ESzRw1ZzZ
legendary
Activity: 1260
Merit: 1116
legendary
Activity: 1260
Merit: 1116
Another nice thing about 0.12 in this area is that mempool transactions will by default expire after 72 hours. Previously they'd stick around until the node was restarted, which made it difficult to predict when the network had forgotten about the unconfirmed transaction and it was time to resend it or create a conflicting one with a higher fee.

The guy who's managed to make non-conforming ideas drop out of the idea-pool of r/bitcoin considerably faster... instantly, in some cases.  Tongue

http://www.badum-tish.com/
sr. member
Activity: 392
Merit: 250
Another nice thing about 0.12 in this area is that mempool transactions will by default expire after 72 hours. Previously they'd stick around until the node was restarted, which made it difficult to predict when the network had forgotten about the unconfirmed transaction and it was time to resend it or create a conflicting one with a higher fee.

The guy who's managed to make non-conforming ideas drop out of the idea-pool of r/bitcoin considerably faster... instantly, in some cases.  Tongue
legendary
Activity: 1260
Merit: 1116
One of them new fangled HD wallets. I get it now. Thanks!
 Following best practices and not reusing addresses has an associated cost.

This and HD wallets are somewhat different issues. The regular non-HD wallets offer multiple addresses in the same wallet too. You just hit create new address, which also creates a corresponding private key in your wallet.dat.

HD or Hierarchical Deterministic means that any address and corresponding private key can be restored from the same initial seed, so if you have that seed safely written down/stored away... you can create new addresses and keys at will, they will all be available to you as long as you have the seed.

With Non-HD, like Classic or Core, any addresses you created after you backed up your wallet.dat... wouldn't have their keys saved in your formerly backed up wallet.dat. You'd need to backup the wallet.dat again to have redundant access to the keys for the new addresses.

I just didn't know they were costing you extra behind the scenes. It makes sense, just never really considered it.


I heard if the transaction isn't confirmed in 72 hours it's dropped from the mempool now. Was this protocol-wide? Or are some wallets doing their own thing in this respect?

https://twitter.com/jgarzik/status/656853984511172609

Another nice thing about 0.12 in this area is that mempool transactions will by default expire after 72 hours. Previously they'd stick around until the node was restarted, which made it difficult to predict when the network had forgotten about the unconfirmed transaction and it was time to resend it or create a conflicting one with a higher fee.
legendary
Activity: 2380
Merit: 1823
1CBuddyxy4FerT3hzMmi1Jz48ESzRw1ZzZ
sr. member
Activity: 392
Merit: 250
One of them new fangled HD wallets. I get it now. Thanks!
 Following best practices and not reusing addresses has an associated cost.

This and HD wallets are somewhat different issues. The regular non-HD wallets offer multiple addresses in the same wallet too. You just hit create new address, which also creates a corresponding private key in your wallet.dat.

HD or Hierarchical Deterministic means that any address and corresponding private key can be restored from the same initial seed, so if you have that seed safely written down/stored away... you can create new addresses and keys at will, they will all be available to you as long as you have the seed.

With Non-HD, like Classic or Core, any addresses you created after you backed up your wallet.dat... wouldn't have their keys saved in your formerly backed up wallet.dat. You'd need to backup the wallet.dat again to have redundant access to the keys for the new addresses.

I just didn't know they were costing you extra behind the scenes. It makes sense, just never really considered it.


I heard if the transaction isn't confirmed in 72 hours it's dropped from the mempool now. Was this protocol-wide? Or are some wallets doing their own thing in this respect?

https://twitter.com/jgarzik/status/656853984511172609
legendary
Activity: 1260
Merit: 1116
One of them new fangled HD wallets. I get it now. Thanks!
 Following best practices and not reusing addresses has an associated cost.

This and HD wallets are somewhat different issues. The regular non-HD wallets offer multiple addresses in the same wallet too. You just hit create new address, which also creates a corresponding private key in your wallet.dat.

HD or Hierarchical Deterministic means that any address and corresponding private key can be restored from the same initial seed, so if you have that seed safely written down/stored away... you can create new addresses and keys at will, they will all be available to you as long as you have the seed.

With Non-HD, like Classic or Core, any addresses you created after you backed up your wallet.dat... wouldn't have their keys saved in your formerly backed up wallet.dat. You'd need to backup the wallet.dat again to have redundant access to the keys for the new addresses.

I just didn't know they were costing you extra behind the scenes. It makes sense, just never really considered it.


I heard if the transaction isn't confirmed in 72 hours it's dropped from the mempool now. Was this protocol-wide? Or are some wallets doing their own thing in this respect?
sr. member
Activity: 392
Merit: 250
One of them new fangled HD wallets. I get it now. Thanks!
 Following best practices and not reusing addresses has an associated cost.

This and HD wallets are somewhat different issues. The regular non-HD wallets offer multiple addresses in the same wallet too. You just hit create new address, which also creates a corresponding private key in your wallet.dat.

HD or Hierarchical Deterministic means that any address and corresponding private key can be restored from the same initial seed, so if you have that seed safely written down/stored away... you can create new addresses and keys at will, they will all be available to you as long as you have the seed.

With Non-HD, like Classic or Core, any addresses you created after you backed up your wallet.dat... wouldn't have their keys saved in your formerly backed up wallet.dat. You'd need to backup the wallet.dat again to have redundant access to the keys for the new addresses.
legendary
Activity: 1260
Merit: 1116
legendary
Activity: 1260
Merit: 1116
^Sounds complicated. Is this a usual thing for people to do? Huh

Not complicated at all, your wallet will do it all in the background.

Say you're going to receive 0.1 BTC. You have it sent to an address. For the next payment you receive, you generate another address. Do it a total of 20 times... your wallet now has 2 BTC in 20 different addresses. Now, you send that 2 BTC from your wallet somewhere else... behind the scenes, your wallet makes a transaction that has 20 inputs and one output (the destination address)... boom, you've made a fairly large transaction. 

One of them new fangled HD wallets. I get it now. Thanks!
 Following best practices and not reusing addresses has an associated cost.
legendary
Activity: 2380
Merit: 1823
1CBuddyxy4FerT3hzMmi1Jz48ESzRw1ZzZ
sr. member
Activity: 392
Merit: 250
^Sounds complicated. Is this a usual thing for people to do? Huh

Not complicated at all, your wallet will do it all in the background.

Say you're going to receive 0.1 BTC. You have it sent to an address. For the next payment you receive, you generate another address. Do it a total of 20 times... your wallet now has 2 BTC in 20 different addresses. Now, you send that 2 BTC from your wallet somewhere else... behind the scenes, your wallet makes a transaction that has 20 inputs and one output (the destination address)... boom, you've made a fairly large transaction. 
legendary
Activity: 1260
Merit: 1116
^Sounds complicated. Is this a usual thing for people to do? Huh
sr. member
Activity: 392
Merit: 250
It ain't English much, but if it helps.
Size    225 (bytes)
Fee Rate    0.00044444444444444447 BTC per kB


Thanks, so 44 sat/byte.

It frustrates me because I semi-regularly send multi kB transactions, that now, require fees that definitely aren't measured in single cents. Following best practices and not reusing addresses has an associated cost.

Hope you don't mind yet another dumb question, but: What are multi kB txs? Multisig?

Nah, just a bunch of inputs from separate addresses.
legendary
Activity: 1260
Merit: 1116
It ain't English much, but if it helps.
Size    225 (bytes)
Fee Rate    0.00044444444444444447 BTC per kB


Thanks, so 44 sat/byte.

It frustrates me because I semi-regularly send multi kB transactions, that now, require fees that definitely aren't measured in single cents. Following best practices and not reusing addresses has an associated cost.

Hope you don't mind yet another dumb question, but: What are multi kB txs? Multisig?
Jump to: