Open BowTiedRadone opened 4 weeks ago
This transaction is treated as a "problematic" transaction, which means that it will not be included in a block. These kinds of transactions always cause trouble, so should be avoided whenever possible. Instead of treating this as a problematic transaction, it should just result in a None
response from get-block-info?
. This change would need to be implemented as part of a hard fork.
Describe the bug Deploying a contract with the
get-block-info? miner-address u0
code works, but executing it causes the miner to reject it, leading to aTooMuchChaining
error on further transactions. While @moodmosaic and I were automating contract deployments and calls, we hit this issue.Steps To Reproduce
stacks-core
and start the node using the configuration located instacks-core/testnet/stacks-node/conf/mocknet-miner-conf.toml
blockstack-cli
binary:func
contract call using theblockstack-cli
binary:Expected behavior We would expect the function to be picked up by the miner and return a proper response.
Environment (please complete the following information):
Additional context The issue was found while running the mocknet, thanks to @obycode's help. Here's the miner log:
CC: @wileyj