Bastian Köcher
Bastian Köcher
@tomaka I don't know why no one is using the api. I was just commenting here based on what I had read/heard around implementing the api. Nevertheless, the point I'm...
> I would actually suggest to see if this should not be considered a Substrate bug before tweaking the spec. Yes that is intended. The node side should not interpret...
> But what you're describing is a Substrate-specific problem, which is that Substrate can't make a runtime call without decoding the output. If Substrate didn't automatically decode the output (and...
> Is this going to check a signature too? Or assume the block was already imported? No this isn't about signature checking. Just to get the block author if the...
> Either already imported, or being authored by validator x. > > In both cases, we only need an account id. Yes for sure. However, I'm still not convinced that...
> otherwise I could take your argument and extract things like weight and length from system as well. If you find a proper way, please do it :heart: > I...
@andresilva do you think that this is problematic?
So, we can close this issue @andresilva?
I don't get this, you can just send the transaction after the required block? Than you ensure that it isn't included before.
> Would be handy to have such support for certain edge-cases though. Some dependencies can be expressed with provides/requires, but if the only dependency is block number then suddenly it...