Ever wanted to ensure that your community knows for sure when they are in the whitelist? Wait no longer! With our new awarded role feature for /configure-whitelist add and /configure-whitelist update you can specify a role users get when they successfully sign up for a whitelist. As soon as they register (or unregister), their roles will be updated to reflect their whitelist status.
You can now include a dedicated image matching your brand, your own logo or something that fits your lore to the /configure-verify announce widget that people are using for quick and easy wallet verification in your Discord.
When you are launching your project you want a easy way to see how much of your project has been minted - both for you and your community. With our new /configure-policy mintcounter command, nothing is easier. Simply point the command to a voice channel of your choice, tell it which policy to track and you will always know where your launch is at.
Have you ever wondered what the current Cardano Epoch is or how much time till your next ADA reward drop? See it in your Discord and let your delegators know as well, with our new widget command /configure-info epochclock, that turns a voice channel into a running epoch clock giving you the current epoch and how much time is left in it.
Resolved bug where the /vote and other poll-related commands would crash if the description would be longer than the Discord-allowed 1024 characters.
Fixed issues with the bot sometimes crashing when it was disconnected from the messaging server.
You asked, we answered! We have had long-standing requests to implement some advanced giveaway tools to the mix and today we are ready to release them into the world. Via the /configure-giveaway add command you can start your journey to sharing exciting raffles with your community.
There are half a dozen of different options for you, including holder-based giveaways, weighted token-based giveaways, drawing unique winners, time-limited and role-specific giveaways, as well as announcing and keeping track of them. Check out the whole offering in our comprehensive giveaway documentation.
Often have you wondered why one of your community members is not assigned a role that they claim they should have. No more! With our new /configure-tokenroles test and /configure-delegatorroles test commands, you can check their eligibility in a jiffy. If you are good for it, you can even assign any missing roles right then and there - but be wary, you will be doing that every other minute if the word gets out 😉.
For both polls and giveways that include only one policy/asset combination and for which that combination is a fungible token, we have now fully integrated the Cardano Token Registry, meaning in those situations you will see your token represented with the correct decimal amount and even ticker name.
We have partnered with a new service to deliver all your IPFS and other NFT-images at lightning speeds. Thanks to NFTCDN.io 's beta test we show newly minted and long-standing announcements that include images from NFTs with high speeds and reliability. Included with that comes support for on-chain NFTs and Arweave as well.
As the NFT ecosystem grows, new ways of ownership appear, and staking your NFTs in a custodial fashion is one of them. We have now integrated with the MutantNFT system to allow users to retain their token roles while their NFTs are staked. Simply set the staking-type parameter when running /configure-tokenroles update and any Mutant-staked NFTs will still be considered owned by the respective staking address. Works with count- and metadata-based token roles!
We have heard from various teams that they invite external, unknown bots into their Discords just to have a shot at custom announcements. Unfortunately, these announcements aren't even in their style - but they do stand out. How would you like your announcements to be on brand? No Problem!
We have added two new commands to allow you to publish all your official projects and policy IDs (/configure-policy announce) as well as a fully generic announcement feature (/configure-social announce). Both commands show your information off in the branded style of your custom bot
Starting a poll is already a multi-step process, so we have always avoided adding complicated steps to allow you to add multiple eligible voting roles on creation and instead allowing only to choose one. This ends now, because with /configure-poll update addrole and /configure-poll update removerole you can now quickly add or remove eligible voters from your existing poll.
We have fixed some bugs with the jpg.store API changing and our sales trackers stopping to work smoothly, except when the sales were offer-based.
This time around we have added a ton of features around ADA Handle! You can now set your own default handle within Discord, which will in the future also be used for the website and Twitter. Simply run /profile defaulthandle and choose from your available handles. The other end of this is the ability to simply right click any user in Discord and see which ADA Handle they have set as their default!
In addition to these new profile settings, you can also resolve any ADA Handle directly within Discord now, or even reverse lookup a wallet or staking address via the brand new /whois command. Check it out and bathe in that sweet green Handle branding.
It is easy to forget that your prepaid phone balance is running out and you will not be able to receive texts until you refill. The same applies for having your community in your ear because token roles all of a sudden are not assigned any more. Fear not, we have added a reminder feature that will send a DM to all admins of the server so you will never forget to renew your Black Edition Balance again
Certain metadata filters failed because their respective tokens were minted with more than just 721-based metadata. We have fixed the logic so it only will consider data from the 721 tag.
The /policyid command does now not crash any more when more than 25 policies are configured on your server.
Fixed bug where voting for polls would crash if the poll had options with more than 100 characters in them.
Preventing sales/listing trackers crashing during add when providing a minimum ADA value smaller than 1.
A mostly invisible change to all users, but quite involved in the amount of effort required, was our migration from the old DiscordJS version to DiscordJS 14, which also uses the new Discord API. The change will allow us to remain compatible with upcoming features in Discord while remaining resilient against potential vulnerabilities. Go check it out on our GitHub, it also includes a lot of work towards migrating to TypeScript!
Making sure that you can add up to 200 policies to any given token role (who on god's green earth needs this many?!).
We have all dealt with people who cannot wait to get their roles. Every time, we used to have to tell them "It can take a few hours". No longer! With the new Insta-roles feature, new community members (i.e. ones that use /verify add or /verify link for the first time) will get their currently qualifying roles immediately after their confirmed verification. If you combine that with our brand-new and very nifty /configure-verify announce widget, new users can have their roles within a few seconds after joining your server. If that is not quick enough, I guess we give up.
We have added a feature that will autodetect abusers of the mangled address feature on Cardano and disable any feature for their accounts when interacting with the bot. Bye bye, suckers.
We have taken our time to implement sales, listing and mint trackers, because we always wanted to build foundational features before catering to our inner degen. But the time is nigh, and with jpg.store adding their own Discord bot, we figured we might as well show the world what we can do with our expertise. And we did. There are a whopping eleven new commands in the Documentation, all under the umbrella of our new Marketplace Trackers and Mint Trackers. Not only do they take seconds to set up, but they're also fully powered up with the ability of our metadata filter system. Sales trackers for specific traits only? Easy peasy!
We have had a lot of users over the last few months, and it is time to make our systems more reliable and resilient. With this upgrade, we're adding a load balancer for our DB sync instances and a second DB sync instance, and move them both from private cloud instances to bare metal servers. This infrastructure change will result in extremely small delays during the epoch boundary as well as resilience in case on of our instances gets out of sync.
Our advanced token role combination feature has been in private test beta with various Discord servers across the last few weeks and aside from a minor issue has shown to be quite stable. We are exteremly happy we can now officially enable you to leverage the four powerful aggregation-type options that become available with our new /configure-tokenroles update command!
Combine your existing roles, policy IDs and metadata filter in new ways to allow roles like “hold one of each color” or “collect one from each policy ID”. Creating cross-project collaborations and make people stand out if they support partner-projects is a surefire and simple way to connect communities across boundaries ♥
In the past you had to recreate token roles if you got the Discord role, count or max-count options wrong. A frustrating experience that is now remedied with the new /configure-tokenroles update command. Simply change your token role settings with this intuitive new feature.
When you are in a gazillion Discords and signed up for 75 whitelists, it can be hard to keep track of all of them. We think so, too, and bring you the upgraded version of /whitelist list. You can now see ALL the whitelists you are signed up for in one spot, on ANY server! Don't believe us? Try it out!
In addition to seeing this data everywhere, whitelist creators can now also set a logo and a launch date for their whitelists, which makes them even more appealing. If a project puts their launch date in via the new command /configure-whitelist update, you almost get something like a whitelist calendar for yourself.
The new logo feature allows projects to show off their whitelists even more attractively, and in the future enable external integrations to showcase current whitelists for your server.
Time zones are tough and even in todays Blockchain-world, where most users have some basic knowledge of UTC time, it would be nice if you could just read a date and time and know what it is. Say no more, we have you covered: With our newest update, the majority of dates and times displayed by the bot, for polls, whitelists and other purposes, will be displayed to you in whatever time zone you have set up for your Discord account. No annoying conversion between UTC and your local time any more!
We have had the ability to download your own whitelists within Discord for a few weeks now, but with today's update you can now also download whitelists shared to you by other servers via /configure-whitelist download. No need to use the API if you do not want to 😉
We like to throw around big words and we believe we do not that we understate the impact of our newest command /ping send by saying: It is revolutionary!. For the first time ever on Cardano, you can send Discord messages to NFTs, wallet addresses or $handles!
Using the verification data available, we allow you to send a Discord message to any user that is also using HAZELnet! All in a secure and privacy-retaining method that allows the recipient to decide if they want to get in touch with the sender, without disclosing any of their information. The bot will send a Direct Message with your Discord Tag and an optional message to the recipient! Even if they have Discord DMs turned off, which is never a bad idea, both senders and recipients can look at their recent pings via the convenient /ping list command.
Don't have your DMs turned off, but also do not want to be bothered by /ping? No problem, the new /profile toggle command will let you turn this feature of as well - your privacy is yours to keep!
With our Voteaire integration earlier this week we have enabled on-chain polls in your Discord with the simple command that is /configure-poll add-onchain. Today, we bring the voting results into the mix. If you have an on-chain poll announcement in your Discord, the current results will be updated every few minutes, the same way it already did with HAZELnet off-chain poll announcements. Watch the results come in, like on election day!
We have shown off various ways to customzie your bot to fit into your project lore, metaverse design or company branding and various projects have been using these Black Edition capabilities for a few months now. However, it always required that one of our team members took the paint brush under your guidance and applied it to your bot. No more! With /configure-settings customize you can do it all yourself. Be the Bob Ross your Discord needs and go with your own style!
The team at voteaire.io is working hard on making on-chain voting available for everyone with a simple user experience. Discord may not be a place to perform on-chain voting, considering you need a dApp-enabled wallet for that, but that does not stop HAZELnet from integration with their solution in a smooth and simply way. Create your Voteaire poll on the website, and simply add the poll via /configure-poll add-onchain. We will automatically retrieve the information from the Voteaire API and show you the description and options within your Discord. A link to the poll is available so your users can go and vote with their wallet. That is what we call teamwork! For now, we only have the ability to retrieve information from the Voteaire testnet version, but once the mainet version is out, we will make sure you can use it in your server as well.
You have seen simple policy-based token roles, ones with multiple policies and even roles with metadata filters. You think you are an old dog in the game. But with our newest addition, you can now take it even one step further: Metadata filter combination roles! /configure-tokenroles update will let you set a filter aggregation type for your existing roles. With it you can choose between four different types:
The default setting is that every metadata filter that you define on a role must be met, for a token to be considered towards the required token count.
With the 'any filter' setting, it is enough for a token to match any of the defined filters, to be considered towards the required token count.
This extremely helpful aggregation type requires that you own one matching token for every single metadata filter. Now you can reward users that hold all seven of your variants, for example.
If you are not interested in metadata filters, but want to encourage cross-project holders or have multiple collections, you can set this aggregation type. It works in conjunction with /configure-tokenroles policies add to ensure people only get the role if they hold one of each of the policies set up for your token role.
When creating polls in the past, you had to manually announce them to post the voting widget. Since we do not want you to have to set yourself a calendar event for two in the night just because of time zones, we have now added a feature that will ensure your voting widget and poll announcement are automatically posted at the poll start time, if you have provided a channel to post in at poll creation. In addition, if the poll has public results, we will regularly (every five minutes) update the poll results in the widget as well. All the information and access you and your community needs, all in one convenient place.
You can announce your polls already, but we know projects definitely want their communities to easily access their whitelist signups as well. That is why we took whitelist announcements to the next level with /configure-whitelist announce.
This simple command will let you post an announcement and signup widget in a channel of your choice, allowing anyone to easily see the requirements and times for your whitelist and sign up for it with the click of a button. They have the option to select from their already verified wallets to make signup even easier!
Are you intimidated by APIs and having to use external tools to get to your whitelists? Do you not need automated access to whitelist information for your mint tool? Would a simple CSV file with your whitelist information be enough for you? We hear you! From today on, you can use the brand new command /configure-whitelist download to get a CSV file with all your current whitelist signups, right here in your own Server. Save yourself trouble of generating an API token and downloading Postman.
It may not always work out with you and HAZELnet. Maybe you do not have time to test it right now, or maybe it just was not the right fit. Now, when the bot is removed from a server, we keep track of it. This helps us to not spend any additional time calculating roles for your server or trying to do anything with the Discord API in regards to your system. Even before this feature, access was simply denied, but we still tried to solve math problems that did not need solving 😉.
Long requested by our users that lost access to a previously owned Discord account was the ability to claim a stake address that is already verified with another Discord account. Well, you need not wait any longer, since /verify add will now let you verify any stake address, even if already registered. Nothing happens until the stake address actually has been verified. Once that is confirmed, the old verification link is disabled (i.e. the old Discord account does no longer have this wallet in their verified list) and the new link established. No duplicate verifications, and if anyone ever claims your wallet, we even keep track of the overwritten verification and can track down what happened. Security comes first!
Sometimes you verify with your transaction but the bot just kind of misses it - often times around the epoch boundary. This is because there are times when we do not have the latest info from the blockchain ledger available within an hour, two or sometimes four. But because your verification times out before that, you then have to verify. We understand that that can be frustrating, and now we have the solution: Verification Extensions. Without you having to do anything, we extend the timeout for verification transactions whenever the blockchain is not in sync with our system. You still might have to wait a little bit longer than you would prefer, but at least there is no need for a second verification transaction.
In collaboration with the team at Deck of Dark Dreams we have added the ability to have claim lists that simply enable the project team to link to a website as part of the claim process. For when your physical goods claiming process does not need to be fully automate with HAZELnet, this simplified option allows you to link a google form for everyone that claims their physical goods they get for owning an NFT.
Fixed bug where voting for polls would crash if the poll had options with more than 100 characters in them.
Polls have been around for about a month now, but we know one of your most desired features was still missing: Announcing your poll and sharing yor results! Well, wait no longer, as we bring you /configure-poll announce today. Not only will this neat new command post an announcement in the channel of your choice, and show the available options, it will also give your users a quick and easy voting widget. With the click of a button on the announcement, they will be prompted for their option or options, and can go about their day again in seconds.
Inspired by a conversation with our friends at pixl.page , we wanted to enable an easy way for projects to collaborate with whitelists. We know a lot of projects do this already, with tedious manual sharing and lots of room for errors. Does that not sound exhausting? We think so, too! Introducing /configure-whitelist share:
With our new sharing and unsharing abilities, you can give another Discord server easy access to your whitelist signups. Your users sign up, they download your signups for their mint. It could not really be any easier!
After rolling out metadata filters recently, we are now powering up the token role capabilities even further! With your new /configure-tokenroles policies add command, you can add multiple policies to one role, allowing projects that are using many different policies for drops over time to have one, convenient spot for holder roles. This also sets the foundation for cross-policy metadata filters and the ability to have roles that require users to hold one (or more) tokens from different policies, also known as combo roles (this feature is not available yet, but will come in Q3 2022).
What could you do if you want to leverage the power of HAZELnet in your own server, but not host it yourself? You can whitelabel us! We have added the ability to add sponsored servers, for which the bot will automatically come pre-customized with your project design and will be Black Edition by default. We are rolling out this feature together with the team from Clarity Protocol and they are rolling out Clarity Bot as one of their own. Get in touch with us in Discord if you are interested in whitelabeling.
Fixed bug where burned tokens polluted the metadata in metadata filter functionalities, leading to roles not being assigned because the bot was looking at the metadata of an incorrect transaction.
A special solution for our friends from Playermint was to allow them to easily migrate their existing verification data, without compromising the integrity of our existing verification data. For this purpose, we have added a dedicated import mechanism that allows users to migrate from other verification bot to HAZELnet. If you need the same type of solution, contact us and we can get you set up.
The highly anticipated and extremely powerful metadata filter system has finally arrived on HAZELnet. You can now assign roles based on one or more metadata traits, allowing you to create roles for example for holders of 3-prop unsigned_algorithms, Degen Crypto Club NFTs with wings and DEADPXLZ with tight hoodies. All the power is at your disposal with our new /configure-tokenroles metadatafilter add command. Click on the command for an extensive documentation with all the different options and a litany of examples for many common metadata scenarios. Add multiple filters together to be even more specific with your roles.
From a technical perspective, the metadata filter is using the powerful JSONPath library to let you define arbitrary rules to extract metadata attributes, and then compare them with a variety of operators to your expected value or values. You can search lists for the presence of specific items, or simply check if certain characters appear in a specific attribute.
We knew this would happen eventually, as we reached a certain number of supported Discord servers. With more than 100 servers using HAZELnet, we had to change the automatic token and delegator role assignment frequency from ten minutes to one hour. This will significantly improve our performance, as the process of aggregating verified wallet information and matching it up with token roles is quite resource intensive. This will also make the addition of metadata filters in the near future less impactful on your bot experience.
We have had a surprising influx in projects using quite a few token roles, and when reaching a certain number of roles, our Discord messages reached the maximum size limit. We have improved the behavior to print out less information when using /configure-tokenroles list. With more than five roles, we only show partial information and instead use a dropdown (for up to 25 roles) or the newly introduced /configure-tokenroles details command. This will come in handy in the near future, when metadata trait filtering is added, leading to even more information for each role.
We have also set a general token role limit of 30 roles for Black Edition servers. If you need more roles in your server, we can increase the limit for each server individually. Just get in touch with us.
Polls for everyone are here! You can now create public (and private) polls with HAZELnet. Administrators can simply run the /configure-poll add command to start a new poll in minutes. You might be wondering: There's many voting bots around, why should I use this one? Because we offer token-snapshot based voting! When you create a new poll, a snapshot of the current token distribution is automatically made for you, so only the people who had tokens at that time can participate. If you want to raise it up a level, you can even add weighted voting, in which the voting power is based on the number of tokens or NFTs owned.
Combined with various other features, like public and private polls, multiple choice votes and the planned enhancements for publishing and reaction-based voting in April will make HAZELnet the best bot for engaging your project's community. They can simply run /vote and make their voices heard.
In the future, after the distribution of the HAZEL token starts, this will be the way community members can vote on which features and tools we develop and build for HAZELnet.
An 🍎 apple a day keeps the doctor away, goes the old adage. Since neither your Discord server nor HAZELnet have an apple-eating feature yet, we came up with the second best option to make sure your server and configuration is healthy: Introducing the /configure-healthcheck command. This simple, optionless command will tell you within seconds if your roles, security configuration and more are up to snuff. If not, it will even tell you remediation steps.
We have plans to enhance this further and help HAZELnet warn you about potential security holes in your server, as much as the Discord API will allow us to report on this information. Another step for us all to a safer experience in the web.
You can now create clean ✨ NFT and token role ladders! With the new maximum count parameter for our /configure-tokenroles add command you can, for example, create roles that go from 1 to 4, 5 to 9 and 10 and up, instead of having the holder of ten or more tokens receiving both of the two "lower tier" roles. Enjoy climbing!
Black Edition is officially launched and will be enforced on April 10th, 2022. This means all limitations and premium features explained on our User and Project pages for Black edition will become available and effective. Our terrific closed beta testers, as announced, receive one year of Black Edition for free. If you want to become a Black Edition user, simply run the /premium command to find out how. Server admins can simply use/configure-premium status to see their discount, latest bill and current balance. We're glad you're taking this journey with us and think the value we provide with HAZELnet can make all of our communities safer and more interactive.
We have added a new server-wide feature to enable migration scenarios when moving from manually verified roles or other verification bots to HAZELnet. Contact us in our Support Discord and we can set your server up with an option so that HAZELnet will not remove unverified accounts immediately, if you are assigning a token or delegation role that is already in use on your server. We can then schedule a gradual transition for you, where your community has time to re-verify while you do not have to do any work to change your role setup, thus reducing the amount of risk (changing roles around in Discord always comes with risks of letting people in you did not want to give access to).
You can now sign up for a whitelist with your $handle! Simply use /whitelist register and put in your handle instead of your Cardano address. The handle will be resolved immediately, not at the time the whitelist is used by the project.
When adding a policy ID via /configure-policy add that is already used on the server, your will now receive a clear indication what is wrong instead of a cryptic error message.
Long-running token assignment jobs sometimes pushed out assignments for servers beyond one minute, resulting in token roles not being properly assigned. Changed it so the calculation as to which servers are due for updating is calculated at the beginning of the job instead when each server is processed.
Fixed a bug where users that joined a server more than one time had their wallets counted multiple times and received roles for counts they did not actually have.
If you have a whitelist registration going and need to close or open it temporarily or permanently, you can now easily do so with the /configure-whitelist close and /configure-whitelist open commands. Maybe you have misconfigured the list or want to close an unrestricted out for your snapshot 📸.
The new /configure-settings features command will let you change your feature sets without needing to use the /start command. Simply add your whitelist features to your existing bot when you are ready to get close to that next minting date!
Advertisements are now available! Show off your project launch by advertising on HAZELnet. Contact us to showcase your project on a variety of Discords.
Black Edition servers will always remain ad-free!
The /verify add flow is much more streamlined when you have already verified on a different server or with a different address from the same staking address. The system will recognize you and immediately link you to the server, without making the user think their stake address is registered by someone else.
Token and delegator role assignments are now evenly distributed across the whole hour, instead of in batches every ten minutes. This makes for an overall much smoother performance profile and users will experience less wait times when interacting with the bot during the 10-minute intervals when assignments are updated.
Various commands have received minor improvements to error out less unpleasantly, for example when adding a whitelist with a duplicate name.
You can now specify an asset fingerprint for automatic token role assignments. To get the role, you will then need the indicated quantity of this token from the policy ID and with the asset fingerprint. This can be used for fungible tokens where multiple different tokens are minted under the same policy ID. If you do not provide an asset fingerprint, all tokens in the policy will be considered for the count. For NFTs, this means you can assign a role based on the verified ownership of a unique specific asset.
The /verify list command can now be used to cancel an ongoing verification, should you realize you do not have funds to verify, or that you have put in the wrong address.
All commands now have a link to their public documentation on this webpage. The link is available through the "Click for help" text attached to the message author. This link is available on branded and unbranded servers.
The /configure-tokenroles add and /configure-delegatorroles add command will now require confirmation if you are assigning them to a role that has more than one member already, to verify you understand the bot will remove the role from users that do not qualify.
Users with more than two verified wallets can use /verify list command successfully again.
Discord servers with many pools can now use the /info command successfully again.
Users do not have to link their account manually if the verification process takes longer than 15 minutes (thanks to @unv_25).
NFTs do not get counted multiple times towards ownership if multiple token roles reference the same policy.
The bot now supports theming and customization per Discord-server. Contact us to have your bot customized if you are running Black Edition. We will make it look to match your color scheme and lore.
The /verify add command gives better guidance when running into the fifteen minute max messaging limit while the timeout due to blockchain congestion is longer than fifteen minutes.
You can now use the pool view ID (pool1...) in addition to the pool hash when adding delegation roles via /configure-delegatorroles add.
Added validation to prevent token and delegation roles with counts/delegation values under 1.
You can now use /verify add with your $handle
The /verify add command will give more clear guidance as to what kind of addresses you need to provide in the call (thanks @bobthebob)
There is now a configurable verification timeout instead of a hardcoded 15 minutes, to allow for adjustment of the parameters while the chain is more congested than usual. I've set the timeout to 60 minutes for now.
Addresses with no UTXOs in them will now correctly be resolved to stake addresses (thanks @bobthebob)
Token policies are now queried correctly again, after the cardano-db-sync was updated to schema version 12.0.0
Added a public REST API to access whitelist data.
Generating REST API authentication tokens via /configure-api generatetoken command.
Stakepools can now be added by their pool hash and pool view identifiers.
Added ability to verify wallets via transactions to yourself.
Bot administrators can add official stakepool and policy IDs to their server.
Automatic role assignments for delegators to their official pools and to holders of their NFT projects.
Implemented Privacy-by-default via slash-commands for all interactions with the bot.
Role-restricted, time-restricted and number-limited whitelists added to the Discord bot.
Discord bot supports localization for English and German.
Added fully Discord-based administrative controls via slash commands.
Added basic commands to interact with the bot and find out information on how to use it and what projects the Discord server officially supports.