Scheduled Publish
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 7.2k
- Forks
- 493
- PR merge metrics
- No merged PRs in 30d
Description
As a creator, I want to publish my content now but not make it available for viewing until a future time.
One way this could be done is to publish the claim and content without the decryption key and with a future release_time. Then at the scheduled time, update the claim to add in the decryption key. The SDK could do the update, or we could create the update transaction in advance and give it to some service. The service would hold the tx and broadcast it at the scheduled time.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue names no files, tests, or entry points. Start by tracing the SDK's publish flow and claim update transaction handling, then determine how a future release_time and delayed decryption-key update should be represented. Done means scheduled content is unavailable until the specified time and the update transaction can be broadcast then.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- blockchain, python
- Domain
- blockchain
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100