Kan Zhang
Kan Zhang
having a separate key work works for me. I'm not opposed to send-builtin, since we already have send-signed. but just built-in works in my head as well.
Also, an addition here, is being able to specify if you want Sealed blocks only
bors merge
this should already be resolved by this commit: https://github.com/onflow/flow-go-sdk/commit/447d9cf0c49ef3d78410ad83f570e2696104d064
Going to close this as it's not caught any traction on the team. If problems similar to this pop up again, will revisit
yeah, I agree, i think currently, it's possible for the access node to still be waiting for collections itself, so cannot yet serve up the collection to the client until...
is this still needed?
AFAIK, we can already freeze accounts with just a tx, without a contract, but maybe i'm missing something.
not sure if this is still the solution we'd like to go with for solving #392 Any objections here?
@fxamacker @ramtinms @m4ksio What's the status on this issue? Getting quite stale.