File expiration

Open
#47 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
rust
Domain
backend

Research direction

No files, tests, or entry points are named. Start by locating the code that stores and evaluates file expiration and inspect how the current block height is obtained. Done should include defined handling for both relative and absolute block expirations, with tests covering the distinction.

Written by the indexing model from the issue text.

Description

An expiration can be set for files. All times are measured in blocks. Expiration can be relative or absolute. For example, relative: 1008 for ~1 week, absolute: 792113
We can know if the expiration is absolute or relative if it's lower than the current block height.

Dominant language
Rust
Stars
3
Forks
0
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from bitmask-stack/carbonado-node

All issues in bitmask-stack/carbonado-node

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.