I guess you don't really understand what stellar is all about.

Removal of unmoved coins will occur at block height 480000 (~March 1) and the estimated new supply is 3.5 million. 1 March.

Is that info correct?


https://tothemoon.live/?IsPast=False&Page=1&Month=0&Year=0&CoinTypes=Bitcoin+Private+%28BTCP%29&SortBy=0

Is there a converter or a program to transform Bitcoin addresses to Bitcoin Private addresses?
I am just wondering how I can get to know if I receive coins from the fork.

For those that may be unaware, there was a 1:1 snapshot that occurred on Feb 28, 2018 at block height 272,991 for Zclassic (ZCL) and block height 511,346 for Bitcoin (BTC), where people who owned Bitcoin or ZClassic were entitled to the equivalent in BTCP (Bitcoin Private), accessed with the same private keys. However, simply importing your private key into a wallet isn’t really enough action to claim your coins, as nothing happens on the blockchain. Coins that have not moved (been included in a transaction) since the snapshot are considered unclaimed and will be burned.

Additionally, in order to avoid a chain split, the removal of unmoved coins will not be done slowly over 2 years but immediately and simultaneously at block height 480,000

Probably best to disable receiving by IP unless you specifically intend to use it.  This is a lot of surface area that nobody uses that doesn't need to be open by default.

In storefront cases, you would typically only want customers to send payments through your automated system that only hands out bitcoin addresses associated with particular orders and accounts.  Random unidentified payments volunteered to the server's IP address would be unhelpful.

In general, sending by IP has limited useful cases.  If connecting directly without a proxy, the man-in-the-middle risk may be tolerable, but no privacy.  If you use a privacy proxy, man-in-the-middle risk is unacceptably high.  If we went to all the work of implementing SSL, only large storefronts usually go to the trouble of getting a CA cert, but most of those cases would still be better off to use bitcoin addresses.

I uploaded this change to SVN rev 156.  The switch to enable is "-allowreceivebyip".

Senders with this version will get the error "Recipient is not accepting transactions sent by IP address".  Older version senders will get "Transfer was not accepted".

I used a different name for the switch because "-allowiptransactions" sounds like it includes sending.  If there's a better name for the switch, we can change it again.

Failed to verify:

Hello Bitcointalk community, this is my first time to stake my bitcoin address after a long while of participating in the forum.
Signed through my Electrum deskstop Wallet.

the btx chart is just one of the sadest things ive seen in crypto.
 

Hi,

there was a swap but i didn't got my new tokens. I had the old tokens on the blockchain (not in a exchange) before the swap but received nothing. You can see that the tokens where on the blockchain at the airdrop date when i recieved the "old" tokens.

> Ibtc swap is moved to 27th of December so that we can create more awareness for the swap. The new contract is ready but some people still have about 3 million ibtc in exchange. The one week grace is final. Please move your ibtc out of etherdelta for swap. Pass it on

Don isn't answering in Telegram channel

What's left to do?

This bug has been around for a long time, and there is currently no definitive solution. Although I am not sure what caused it, many people have encountered similar situations.
There are many solution ways, you can try.
1. Back up your wallet, then uninstall your semux wallet, delete all the data, and reinstall it.
2. Quit your VPN, if you don't use VPN, try changing IP.
3. Delete the data about the network connection in the Regedit and restart your computer.
4. Restart the router.
5. Reinstall Window.

Just quoting myself. Well played, OP.

Much more orphans. If you're using POW, the delay in the block relays would be much more significant than the block interval.

If the number of required confirmations remains the same, the security of the merchant accepting the transactions would decreases significantly. As compared to before, less resources is required to attack the chain and double spend your own transaction. I can't think of any significant advantage to lowering the block time to that amount.

-----BEGIN BITCOIN SIGNED MESSAGE-----

Bitcointalk username:whitembeee
Bitcoin address:1HBkiQ84ahfNEAapDPtvxdp8akJxqU9N1V
 Today is september 22, 2018

-----BEGIN SIGNATURE-----

1HBkiQ84ahfNEAapDPtvxdp8akJxqU9N1V
H74Jw9oJo8/qV+A7Oq1gBoNsMOX4/n3nSCHiKx+eBK5ZHUpg/rybV3Izc1GM1pILAuZ+NY06ZMBKwgwjH0CEhas=

-----END BITCOIN SIGNED MESSAGE-----

-----BEGIN BITCOIN SIGNED MESSAGE-----

Akun bitcointalk:whitembeee
Bitcoin address:1HBkiQ84ahfNEAapDPtvxdp8akJxqU9N1V
Tanggal sekarang : 22 september 2018

-----BEGIN SIGNATURE-----

1HBkiQ84ahfNEAapDPtvxdp8akJxqU9N1V
H74Jw9oJo8/qV+A7Oq1gBoNsMOX4/n3nSCHiKx+eBK5ZHUpg/rybV3Izc1GM1pILAuZ+NY06ZMBKwgwjH0CEhas=

-----END BITCOIN SIGNED MESSAGE-----

Oh sure. You can see the profitability here: http://dev.pywaves.org/generators/
In the column "Average Gen. Balance" shows the amount on the balance of the Full node, and in the column "Waves fees" - the approximate number of Waves, which this Full node receives for the mining per day. To run the mining now the minimum necessary balance of 1000 Waves.