W
by
James Ruffer
0 (0 reviews)
Web3devs Stacks Access Plugin
Limit access to Posts and Pages based on user's Stacks wallet content (ex. STX, Fungible Tokens or NFTs).
Web3devs Stacks Access Plugin ranks #68,598 among WordPress.org plugins with 0+ active installations, and was last updated Jul 14, 2022. Data from WordPress.org, refreshed twice daily — see methodology.
Tested up to WP 6.0.16 (Current: 7.1.2)
v1.0.3
Current Version v1.0.3
Updated 4 years ago
Last Update on 14 Jul, 2022
Refreshed 7 hours ago
Last Refreshed on
No update in over a year
Rank
#68,598
—
No change
Active Installs
0+
-100%
KW Avg Position
107
15 worse
Downloads
1.2K
+2 today
Support Resolved
0%
—
No change
Rating
0%
Review 0 out of 5
0
(0 reviews)
Next Milestone 10
0+
10+
48,858
Ranks to Climb
-
Growth Needed
8,000,000
Active Installs
Pro
Unlock Exact Install Count
See the precise estimated active installs for this plugin, calculated from real-time ranking data.
- Exact install estimates within tiers
- Track install growth over time
- Milestone progress predictions
Need 10 more installs to reach 10+
Rank Changes
Current
#68,598
Change
Best
#
Downloads Growth
Downloads
Growth
Peak
Upgrade to Pro
Unlock 30-day, 90-day, and yearly download history charts with a Pro subscription.
Upgrade NowReviews & Ratings
0.0
0 reviews
Overall
0%
5
0
(0%)
4
0
(0%)
3
0
(0%)
2
0
(0%)
1
0
(0%)
Track This Plugin
Get detailed analytics, keyword tracking, and position alerts delivered to your inbox.
Start Tracking FreePlugin Details
- Version
- 1.0.3
- Last Updated
- Jul 14, 2022
- Requires WP
- 5.9.2+
- Tested Up To
- 6.0.16
- PHP Version
- N/A
- Author
- James Ruffer
Support & Rating
- Rating
- ☆ ☆ ☆ ☆ ☆ 0
- Reviews
- 0
- Support Threads
- 0
- Resolved
- 0%
Keywords
Upgrade to Pro
Unlock keyword rankings, search positions, and detailed analytics with a Pro subscription.
Upgrade Now
Frequently Asked Questions
Common questions about Web3devs Stacks Access Plugin
Hiro Wallet only.
Short answer: no. Long answer: Xverse - maybe. Wallet Connect compatible wallets - maybe. If a wallet is compatible with Stacks.js, then it should work. Hiro Wallet is the de facto standard for Stacks 🤷
None. The ones that we would probably need for this to be 100% PHP based are: secp256k1 - but it's experimental, requires manual compilation and it's development is staled c32check - it's Stacks' variant, so has to be reimplemented in PHP stacks.js - but in PHP :) Since none of the above is available at the moment, we've moved the required dependencies to a third party service that simply takes the signature and calculates Public Address used to sign it.
0 (zero). There's no cost, because there's no transaction involved. Signing a secret phrase is the wallet's built in functionality. It happens "locally" and is not published to the blockchain, therefore does not end up as a transaction.
We don't. We don't need it and we don't access it. We need your wallet's public address. To prove you OWN the address, we need you to use the wallet to sign a secret phrase for us (your wallet uses your private key to do it - the key never leaves your computer!). Your wallet contents is publicly available information. If you know a wallet's address, ex. ST24YYAWQ4DK4RKCKK1RP4PX0X5SCSXTWQXFGVCVY you can see it's contents in blockchain explorer or via Stacks API - that's how we determine if you own configured tokens. See: - API view - Stacks Explorer If we (or ANYONE ELSE) ask you for your private key or seed/mnemonic phrase - THAT'S SOMETHING you should be worried about
It's due to a bug in Hiro Wallet, see here. Basically, when connecting Hiro Wallet for signing, the account selection screen sometimes makes no effect and your current account is selected. Pay attention to account public address shown at the top of the screens to make sure you're signing with desired account. Otherwise - switch it in the wallet, before connecting (refresh the page to "disconnect" your wallet if needed, sometimes you may need to close your browser (clear session cookies))
Yes. Message signing (which we use to derive your wallet's public address) is a relatively new feature in Hiro Wallet and Stacks itself and it's been published prematurely :) There are (were) problems with: - message signing in a way that prevented users from deriving public address from signatures (see here, here and here) - incompatible secp256k1 signature orders (vrs vs rsv) (see here) The good thing is: it's a known problem The bad thing is: when it's fixed, chances are our plugin will stop working until we make it compatible with the new versions of Hiro Wallet and Stacks.js