🌴 Friday Recap — 24th of November, version 1.1.7

PaLM AI
5 min readNov 25, 2023

It’s getting hard to think of unique forms of hello to start the recap articles with. Let’s go with a big Greetings this time!

The past week has been a busy one — we have again achieved our development goals, expanded our community and reach and fulfilled promises. It is a great feeling to have another successful week behind you, whether you are a developer or not. In this recap, will focus on the PaLM AI utility systems (read that right) developers’ past week, where we added Google Search Smart Summarization, finalized token tracking & updates, improved the User Interface, prepared the grounds for the 1.2 update and finished the technical development of our revenue share model.

Command Polishments

A list of commands viewed from the bot's menu, some fattening of the command palette is apparent. Question is: we communicate well enough that the users can stay ahead of the updates?

Commands have been revamped. We took inspiration from the style of most widely used utility bots, where usually the first letter of a word used to describe the command functions as the command handler. However, we are doing it with a twist and still retaining some of our own style, and indeed experimenting still with what we feel to be the most intuitive UI. For example, the devs debated whether /a was the intuitive command for “analyse” and if the command /help should be similarly /h. At some point in the future we will probably settle for the style most well received by the community.

Google Search x PaLM AI

In my front of development, the gruesome and intertwining backend of functions containing database queries, API calls and threading loops conflicting with callback functions, we did some magic to enable the Google Search Smart Summarization function, which we dubbed Google Search X PaLM AI.

Lovely (I do mean it) member of our community was one of the first to play around with the /g function. As evidenced, the access to web real-time data and smart summarization of the article is on point.

What the /g function does is it takes the four best hits from your Google Search, and summarizes them for you both as a topic & each article / page / etc. individually. It is a powerful tool to gain up-to-date knowledge quickly. It is also quite experimental in essence — we wanted to go for a less traditional approach. I always got disappointed when ChatGPT (with Bing) just decided to scrape one random web page and base it’s information off of that when I asked it to browse the web.

The four best hits + summarizations is the optimized way that we found most effective. Over 4 we felt was too spammy, 2 we felt was too little, and 3 seemed too cheap. In conclusion it is one of the most advanced features on PaLM AI as of writing. But what else did we work on?

Token Name & New Tracking

The links in the message field take you to DexTools to double check!

It is no longer necessary to use the contract address if you know the name or symbol of the token. This is a much needed QoL update and will go perfectly with 1.1.8, when there will be simply too much information to keep pasting addresses around.

No caption. Needed.

The command-free input side of the bot has also been improved. It parses an ERC-20 address automatically and executes the supposed function.

Now, the final thing left to do is to with the other commands replace the need for a CA or pair address with a token name. Which is in the works!

Road to 1.2.0 & Revshare

The roadmap steadily progressing towards 1.2

While the utility development remains a priority, half of the team this week detached themselves to work on our revenue share contract & dashboard, along with the 1.2 Update. This included adding in many beta tester commands and teasers, such as /news.

As of late Fridat, our Revenue Distribution contract is now live on the Ethereum mainnet. What this means is that the revenue share the community has been waiting on is just a few unlocks away. (and we are taking working towards it very seriously)

The 1.2 update goes directly hand-in-hand with the revenue share sources and it will be detailed how
revenue share is sourced on the dashboard and what is your predicted percentage of it.

There is no specific amount you need to hold a specific amount, no need on your part to do anything except claim (and prove ownership) of your share and it will be paid in Ethereum as it is mostly sourced in Ethereum (other options being USDT on ERC-20). To repeat, revenue is sourced primarily as ETH, which is then directly passed on to the pool of revenue to be shared.

We will offer three types of ways to utilize your PaLM tokens: LP staking, token staking & the claiming of revenue share. All can be pulled out of without any penalty to the holder, as we have a rewards-first approach. Now that the token is well utilized, we can turn our sights to the PaLM AI bot itself— and the many use cases and platform variations of it to come.

Conclusion

That is it for this week’s late Friday AMA. May your weekend be peaceful. And for us grinders, keep going at it. Laid back or not, on this journey we are all going to make it 🌴

Hope that was inspiring. Thank you for reading!

- $PALM Team

--

--

PaLM AI

$PALM: Multi-platform PaLM AI chatbot uses @Google AI tech for conversations, coding, and image generation, focusing on accessible AI and revenue sharing. 🌴