You can write your own contract which can store string (representing your address) in eosio::multi_index table. Table can be accessed easily by RPC call, because the changes are stored in state. (not need to replay all actions to achieve current state)
Can any of these things happen to EOS or something similar?
BPs can certainly decide not to include transactions. This is particularly dangerous because not including transactions means the BPs cannot be voted out, as votes are communicated through transactions. If 1/2+1 BPs refuse to include transactions, a hardfork would be required to address the issue.
Dice announced in December that they would create pegged EOS tokens for Bitcoin, Ethereum, and USDT.
In their announcement, they said:
The user deposits the corresponding currency into a specific gateway
address. They will be issued an equal amount of the EOS-based coin.
For example, a BTC deposit will give the same number of EOSBTC coins
on EOS. ...
No, cleos is not a wallet software; it's a CLI tool interfacing with nodes and wallet services.
EOSIO software is akin to Bitcoin Core, which comes with bitcoind, bitcoin-qt, and bitcoin-cli. These are comparable to nodeos, keos, and cleos, respectively. So, if you want to draw parallels with other blockchains, cleos is somewhat similar to bitcoin-cli in ...