Link
Link, running on that computer. Phones, and any other computer, will see “No Link detected”.
Web3 security
Spam bot, brute force & phishing protection.
A block of HTML you paste onto a page. A visitor pays a small amount from Link, the wallet on their own computer. Until that payment is made, the page shows a Continue button and nothing else.
After the payment, the cover lifts and the page is visible. The payment is one transaction. It pays you, pays a house fee, and writes a signed record of who visited and which page they opened.
Link, running on that computer. Phones, and any other computer, will see “No Link detected”.
A published @nexusnode.link paymail in that Link.
Link listens only on that computer.
Your @nexusnode.link paymail, or a 1… payment address.
What the visitor pays you. Minimum 200 sats. Maximum 1000.
A short note stored in the on-chain record. Do not use a | character.
Where to send a visitor who does not have enough funds, or who cancels.
Off or on. Off is the default.
Link adds a house fee of 500 sats, paid to webgate@nexusnode.link. The HTML cannot remove that fee or send it to another address. Changing the fee is a change in Link, not in this block.
If Link is not running, the page says No Link detected and stays there, so the visitor can start Link and press Continue again. If the wallet cannot cover the payment, the page says Not enough funds, waits a moment, and then opens the deny address. A cancelled payment does the same.
The transaction outputs are the amounts: yours, and the 500 sat house fee. The block time is the time. The note in the transaction is short. It contains the type web_gate, the visitor’s handle, the page origin, the page path, your message, a nonce, and a signature. The path does not include a query string.
The nonce in the sample block is a placeholder. That is enough when you only want the page covered. A site that must refuse a repeated payment replaces link_nonce with a new value each time the page is served, and accepts a form only after it has seen that value in the transaction.
No plugin is required.
data-link-to, data-link-sats, data-link-message, and data-link-deny.Leave data-link-auto-pay as off when the visitor should press Continue, and then confirm the payment in Link. Set it to on when the page should pay as it loads, with no Continue click and no question in Link, for as long as Link’s own limit allows. That limit is 30 seconds between these payments, 3 a day for one site, and 8 a day across every site. After the limit, Continue returns and Link asks. The page cannot raise the limit.
The address wp-login.php is not a page you can edit. A Custom HTML block cannot be placed on it. The Code Snippets plugin prints this block on that screen. You do not need to rename the login address.
data-link-to and the other fields inside that HTML. Do not add data-link-post. After payment, the cover lifts and the WordPress username and password fields are already on the page.wp-login.php. Continue should sit over the login form.If that window is blank, return to the tab that is still logged in and deactivate the snippet.
Open the snippet with this. Do not add a <?php line of your own above it. Code Snippets already runs as PHP.
add_action('login_footer', function () {
?>
Paste the HTML block here, then close the snippet with:
Copy this into a Custom HTML block on a normal page. On the login screen, paste it between the two PHP lines above. It is shown as code, so it does not cover this page.