5

You are violating one of the basic concepts of blockchain. You can't remove anything! If the contract has a method in place for disabling its functionality that's fine. However, it will always remain on the blockchain.


4

I assume you deployed it on the Main Net using MetaMask. Probably the gas limit of the transaction was too low. Otherwise the gas price was to low. Please send a screenshot of your MetaMask transactions, in case above didn't fix it.


3

This seems to be a remix bug. When you deploy it using web3 or so it should work properly. Everything should be fine. As the other answer stated you can bypass this problem.


2

It is not possible for a Smart Contract to trigger itself. However, you could use an external service like the Ethereum Alarm Clock which will trigger the Contract for you.


1

The transaction does not have a "to" so the EVM will try to deploy a new contract using the data field as bytecode. You are sending in the data field the following: 0xa9059cbb0000000000000000000000000764edccd0278ee60c421148b8bab812306d90d50000000000000000000000000000000000000000000000000de0b6b3a7640000 Now 0xa9 is not a valid opcode and the EVM will halt ...


Only top voted, non community-wiki answers of a minimum length are eligible