I have experienced new name registration rate limiting and I know many other developers have as well. The confusing thing I’ve noticed now and had confirmed by someone else is that the rate limiting does not appear to be tied to ip address.
In looking at the subdomain registrar code base, there is mention of ip addresses in the config file, but I’ve seen new names blocked for me and others even when trying to register them from alternate ip addresses (through vpn for example). Yet interestingly, the name registration works if done directly through the hosted Blockstack browser.
So, I’m just looking for clarity on what triggers the 409 response for registration of Blockstack sponsored names.
The subdomain registrar is configured to limit registrations by IP and minimum name lengths. In the case of good_45633 it seems like the IP has registered many names already:
{"level":"warn","message":"good_45633 failed spam-check: IP address \"...\" already registered .. subdomains.","timestamp":"2019-09-03T21:33:35.632Z"}
It’s not a per day limit — it’s cumulative. Once you’ve registered 20 names with an IP, you can’t register more. This is only on the .id.blockstack registrar, if you run your own, you can turn this limit off.