Laxmi Prasad Oli
Laxmi Prasad Oli
This will be implemented in the blobber. Blobber can charge client based on whether they subscribe for gdpr reporting. Generating gdpr from writemarkers will pressurize sharder on both cpu and...
This PR is replaced by https://github.com/0chain/0chain/pull/2044 as the requirement of blocks management changed as well.
@Sriep Can you please explain this a bit more with some appropriate links?
As per Whitepaper a write marker contains client id, blobber id, allocation id, timestamp, file root, the hash of the root directory on the file system, prev file root, write...
Yes it should work. Any filemeta hash signed by user, stored in `reference_objects` table will do. For some path, client needs to send signed metadata of all subdirs along the...
Maybe add a test to create 100 directories concurrently and raise error if there is allocation mismatch error in any goroutine and consider it ok if context deadline or timeout...
@guruhubb I would like to propose one simple solution for this. Currently we don't have consistent datetime values of `created_at` and `updated_at` among blobbers. Its better to have same datetime...
@moldis Any progress on this?
@peterlimg @cnlangzi What should be done to this issue?
@YarikRevich Can you explain this? We already do have this functionality in zbox.