Aramik
Aramik
I think we are already doing that proof of ownership during writes for schemas that have `SchemaSetting::SignatureRequired` setting.
You are correct, from frequency perspective we are storing each item as a byteArray and we don't care if the underlying data is a public key or not. I think...
> LGTM. However, I’m a bit unclear on how this will benefit the client. It might be more effective for the client to keep track of transactions that have not...
Our RPC returns current hash once a page is retrieved. Not sure if we need an additional RPC.
> I think one question to answer is: is it possible to read only the first N bytes of a page? I hate to have to read the entire page...
We deployed reverted this but not sure why it's in a blocked state
> We should consider removing all the events and just do off-chain websocket event filter registrations. I'd like to know more about this. I did some benchmarks and it seems...
@enddynayn yeah, in that case we need to be really careful about how our benchmarks are setup, since there might be some hidden costs that are not reflected there.
moved to https://github.com/frequency-chain/frequency/pull/2137
Might be an issue with versioning?