Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

[FEATURE] <dev-when-staked>

Open
#118 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
20/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
typescript
Domain
blockchain, frontend

Research direction

Start by reviewing the proposed dev-connection element (#126) and the amp-list architecture referenced in the issue. Define the component behavior and acceptance criteria for staking verification, conditional src requests, template rendering, and placeholder content before implementation; no files or tests are identified.

Written by the indexing model from the issue text.

Description

enhancement
Detailed description

This issue doesn't have a more in-depth spec, it just suggests a feature.

By declaring HTML as follows, the viewer's staking position is verified, the request to src is made only when the require condition is fulfilled, and its response is applied to the template child element and rendered.

This architecture is based on amp-list.

<dev-when-staked connection="CONNECTION_ID" destination="0x..." network="NETWORK_NAME" require="300" src="https://example.com/data...">
    <template>
        ...
    </template>
    <p>Placeholder while waiting to meet require</p>
</dev-when-staked>
Options
  • *connection: the id of dev-connection element #126
  • *destination: the address of the staking destination
  • *network: the network name
  • *require: the minimum staking amount to unlock content
  • *src: the content source
Context

<dev-when-staked> is useful for achieving staking paywalls with minimal coding.

Possible implementation

No response

Additional information

No response

Code of Conduct
  • I agree to follow this project's Code of Conduct
Dominant language
TypeScript
Stars
7
Forks
1
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 dev-protocol/dev-elements

All issues in dev-protocol/dev-elements

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.