Bitcoin can't stop incoming transactions to a specific address.
However you can block transactions from an address; restricting UTXOs from being spent until a certain time passes.
Topic: A way to not accept coins when a certain time passes at Bitcoin's address (Read 166 times)
March 23, 2018, 03:59:57 AM
March 23, 2018, 02:55:08 AM
Ethereum can't do that, Bitcoin neither.
OpenZeppelin is not a part of the ethereum blockchain but a library built for making/writing smart contracts.
Depending on how the code is written, stopping the trade of a Token is possible. But they cannot block ethereum address from receiving other tokens or ETH.
It's the same as freezing of accounts to disable ERC20 Token distribution or trades which is "a must" for Smart Contracts.
OpenZeppelin is not a part of the ethereum blockchain but a library built for making/writing smart contracts.
Depending on how the code is written, stopping the trade of a Token is possible. But they cannot block ethereum address from receiving other tokens or ETH.
It's the same as freezing of accounts to disable ERC20 Token distribution or trades which is "a must" for Smart Contracts.
March 23, 2018, 02:41:01 AM
With Ethereum, you can stop receiving coins after a certain time on a Smart Contract, but can Bitcoin do that?
Ethereum often finds methods and sources for "cloud-sale" on WEB, but we are investigating whether Bitcoin can do the same thing ,,,
https://github.com/OpenZeppelin/zeppelin-solidity/tree/master/contracts/crowdsale
Even without saying "cloud-sale"
"How to can not deposit money to the specified address after a certain time"
I am glad if I can do it, is it possible such a thing?
Ethereum often finds methods and sources for "cloud-sale" on WEB, but we are investigating whether Bitcoin can do the same thing ,,,
https://github.com/OpenZeppelin/zeppelin-solidity/tree/master/contracts/crowdsale
Even without saying "cloud-sale"
"How to can not deposit money to the specified address after a certain time"
I am glad if I can do it, is it possible such a thing?
Jump to: