

The GLYPH token has reached 1.32 SWAP.HIVE per unit.
I would like to remind you that you can sell your tokens if you have any in stock, or wait for the upcoming improvements that should be introduced over the next few months.
By mid-September, the token should include a staking feature. Although this feature will not be very useful on its own at first, each additional option added to a token costs 1,000 BEE.
The staking feature will therefore be the first step. I will then need to set aside another 1,000 BEE to fund the second step: the possibility of delegation. This feature will probably not be very useful on its own either, but it will prepare the way for the next stage of the token’s development.
Supporting My Projects
If you would like to support my projects, you can delegate BEE or HP to me through the following website:
👉 https://hive-engine.com/lease
In exchange, you will receive BEE.
⚠️ Please note: you must use https://hive-engine.com/lease in order to receive your rewards.
Here are a few screenshots showing the available offers:



Thank you to everyone who is already participating through the system at https://hive-engine.com/lease.
I hope you enjoy this part of the program. Once everything has been properly set up, the system will continue to be improved and updated over the coming months.
Next Distribution
The next distribution will take place in a few hours for everyone who has received a vote from this account.
The bot is waiting to exceed 300 votes before launching.
👉 https://hive-engine.com/lease
For the bot to vote for you and for you to receive 0.0003 GLYPH, the following conditions must be met:
- The account must have enough voting mana available.
- You must have a positive reputation.
- You must publish an article containing 500 words or more.
Only actual words are counted: spaces, numbers and punctuation marks are not taken into account. For example, “500” will not be counted, while “five hundred” will be counted. - You must not be blacklisted.
The bot follows the @hivewatchers list, even though it does not currently downvote accounts. This could change in the future. I also have my own blacklist, created at the request of certain people who had very good reasons for excluding specific accounts. - You must not publish NSFW content.
This feature still needs to be checked and properly configured. - Your post must not be muted.
I also still need to verify that this function is working correctly.
You can contact me through PeakD’s internal messaging system or directly in the comments if you notice that a vote was made when it should not have been.
Likewise, you can let me know if you think the bot missed your post, especially because its voting mana was recharging.
All posts and tags are accepted, except for NSFW, pornographic, sexual or similar content.
A Few Personal Updates
For the time being, I may be difficult to reach, but I will try my best to reply whenever possible. I have returned to a real-life job in order to finance my daily life. ^^
I am also continuing to accumulate HP in an attempt to reach 20,000 HP, with the goal of starting curation activities.
The account is called @we-are-ai because all the bots currently running were largely coded by artificial intelligences.
The texts are also corrected, improved and reworked with the help of AI. I have other activities in which I try to delegate as many tasks as possible—whether real-world or virtual—to these little bots.

Posted Using INLEO