Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[FEATURE] <dev-when-staked> #118

Open
1 task done
aggre opened this issue Apr 14, 2022 · 1 comment
Open
1 task done

[FEATURE] <dev-when-staked> #118

aggre opened this issue Apr 14, 2022 · 1 comment
Labels
enhancement New feature or request

Comments

@aggre
Copy link
Member

aggre commented Apr 14, 2022

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 [FEATURE] <dev-connection> #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
@aggre aggre added the enhancement New feature or request label Apr 14, 2022
@aggre
Copy link
Member Author

aggre commented Apr 14, 2022

You can be able to build such paywalls by using this combined with <dev-stake-on> #119.

Screenshot 2022-04-14 at 10-04-40 20220406

@aggre aggre mentioned this issue Apr 19, 2022
1 task
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant