how to stop? I have bitcoin-core and it keeps downloading new block

[girlbtc.com]

how to stop? I have  bitcoin-core and it keeps downloading new block

In other words. I want to use some command  but don't want it to download automaticly, anyway to stop it from updateing?while my internet is good.

[1715217417]

1715217417

[1715217417]

1715217417

[longbob72]

In Settings > Options > Network, check "Connect through SOCKS5 proxy" and set the IP to 127.0.0.1 and reset bitcoin core.

[QuintLeo]

If bitcoin core DOESN'T regularly download blocks to update the blockchain, it becomes unsynchronised and you can no longer do anything with it 'till it IS synchronised again, as it doesn't have the correct and up-to-date information it needs to DO anything else.

 If you want it to stop for a bit, just shut it down.

[longbob72]

If bitcoin core DOESN'T regularly download blocks to update the blockchain, it becomes unsynchronised and you can no longer do anything with it 'till it IS synchronised again, as it doesn't have the correct and up-to-date information it needs to DO anything else.

 If you want it to stop for a bit, just shut it down.

Most of bitcoin core's function can be used without being fully synchronized. Including sending bitcoins.

[QuintLeo]

Odd, every time I've tried to use bitcoin-qt to send coins when it wasn't synched, it refused to do so.

[longbob72]

Odd, every time I've tried to use bitcoin-qt to send coins when it wasn't synched, it refused to do so.

If you haven't synced up to the point where the output transaction that you're using shows up on the blockchain, you'll not be able to send bitcoins without creating and signing the transaction manually via createrawtransaction and signrawtransaction commands. There's a thread about this here.

[QuintLeo]

Seems like a major security hole though, to allow a send transaction when you're not syncronised.

[DannyHamilton]

Seems like a major security hole though, to allow a send transaction when you're not syncronised.

Why?

As long as the transaction is valid, there is no security hole.

if the transaction is not valid, then the network will reject it, so there is still no security hole.

[QuintLeo]

Client shouldn't allow the transaction to be created in the first place if it doesn't KNOW you have the coin.

[DannyHamilton]

Client shouldn't allow the transaction to be created in the first place if it doesn't KNOW you have the coin.

If you KNOW you have the coin, why should the client care?

If you don't KNOW that you have the coin, then it's your own responsibilty to create valid transactions if you aren't going to use the standard user interface on the wallet.  Again, why should the wallet care what transaction you create?

If you use the standard user interface on the wallet, then any well written wallet won't create an invalid transaction for you.

[QuintLeo]

Because the CLIENT doesn't know for sure if you still have the coin.

If it is not fully synched, it CAN'T determine if the transaction is valid or not - which is why a WELL WRITTEN wallet would not let you create such a transaction.

[DannyHamilton]

Because the CLIENT doesn't know for sure if you still have the coin.

It doesn't need to.

If it is not fully synched, it CAN'T determine if the transaction is valid or not

It doesn't need to.

It just needs to broadcast it and see what happens.

- which is why a WELL WRITTEN wallet would not let you create such a transaction.

A well written WALLET (that creates transactions for you) shouldn't create invalid transactions.

A well written network CLIENT should allow me to communicate with the network and should broadcast what I ask it to broadcast.  It can have safeguards that prevent me from accidentally creating a denial of service attack or other things that I might not want to do, but but should allow me to turn those safeguards off if I WANT to be able to do something that the client typically prevents.

Note that most wallets are built with the assumption that the wallet is in control of the private keys that the wallet knows about.  If a user chooses to do something that isn't supported by the wallet (such as porting those private keys to other wallets or manually creating their own transactions), then the wallet may allow you to try to create a transaction with bitcoins you don't control any longer.  The bitcoin network will reject the transaction, but even with a fully synchronized wallet, if you've ported your keys elsewhere, it would still be possible to create invalid transactions.

[Jdh13579]

I currently have money sitting in my bitcoin core account but it doesn't show the money because bitcoin core will not finish the sync. Does anybody have any advice?

[--Encrypted--]

I currently have money sitting in my bitcoin core account but it doesn't show the money because bitcoin core will not finish the sync. Does anybody have any advice?

what do you mean by "will not finish the sync"? if it is stuck and not moving at all then post the debug log. preferably in a new thread.