=== Brave Payments Verification ===
Contributors: pfefferle, mrose17
Tags: well-known, well-known-uris, discovery, brave
Requires at least: 3.5.1
Tested up to: 5.3.2
Stable tag: 1.0.4
License: MPL2
"Well-Known URIs" for WordPress!
== Description ==
This plugin creates the /.well-known/brave-payments-verification.txt file.
You will need 'manage_options' capability in order to use the Settings page for this plugin.
NOTE: as with all plugins, once you are no longer using the plugin, you should de-activate it.
This is a good security practice.
== Changelog ==
= 1.0.4 =
* Optimized for Brave Publisher Verification
== Installation ==
1. Upload this plugin to the `/wp-content/plugins/` directory.
2. Activate the plugin through the *Plugins* menu in WordPress.
3. Go to *Settings > Brave Payments Verification*, enter the verification code you received, and click on `Save Changes`.
4. Once you have received an e-mail that your site has been verified, deactivate this plugin.
== Frequently Asked Questions ==
= It doesn't work =
Please check that your .htaccess file is configured correctly (it should contain "RewriteEngine On").
On a fresh Wordpress install, you can generate the .htaccess file by going to Settings -> Permalinks,
choosing a permalink format and clicking Save Changes.
You can also debug rewrite rules with with https://wordpress.org/plugins/rewrite-rules-inspector/
It can be a challenge to make a foolproof wordpress plugin, so we'd like to set up a honeypot to encourage Anons from the Internet to do friendly security testing on our app.
Let's set up a wordpress installation, vanilla settings, and add the brave payments plugin.
Then we'll add a private key to a cryptocurrency wallet with some monies in it, a bounty for anyone who manages the pwn the honeypot, and we'll put a nice welcome message on the front page. If they win, they can also report it to us on HackerOne for bonus points.
The plugin adds an entry to the WP admin panel at: Settings > Brave Payments Verification
However most plugins add entries at the top level, so our style could be unexpected UX.
To help users find it, let's add an annotated picture in the readme / plugin landing page.