I Dunno... but I made a GitHub Repo

A few days ago, I shared a post about building a trading bot for PeakeCoin. It was raw, real, and to the point: I was trying to automate SWAP.BNB trades using the beem
Python library, and running into key verification issues, I just couldn’t solve.
🔗 Original blog: I Asked for Help. I Got Silence. So I Started Building Anyway.
And something cool happened.
@millhouze told me to create a GitHub to work on it together. Maybe get some help debugging it, or even contribute directly. And that made sense. It’s one thing to talk about a problem—another to show it.
So I did just that:
🔗 GitHub Repo: peakecoin_bnb_bot
Do I Know What I’m Doing with GitHub? Not Yet.
I’ll be honest—I don’t really know how to use GitHub. Not fully. I understand the basics: uploading files, committing changes, and sharing code.
But there’s a lot I don’t know:
- How to write a proper
README.md
- How to create or respond to Issues
- How others contribute to my code or suggest changes
- How to keep everything synced when I'm editing locally vs online
Still, I created the repo. I’m figuring it out as I go.
Why I’m Sharing This
Because someone else out there is probably in the same spot.
You’re building something cool. It’s half-working, half-broken. You’re not a Git wizard. But you want help, or maybe just someone to say, “Hey, good work so far.”
That’s what I’m doing now. I’ve put the bot on GitHub, even if it’s messy. I’m opening myself up to feedback, to learning, and hopefully to building something that works, not just for me, but for others who believe in projects like PeakeCoin too.
If You Know GitHub—and Want to Help
I’m all ears.
Feel free to:
- Suggest improvements
- Open an issue if you spot something
- Teach me how to make the repo more useful
- Or just let me know you're watching it grow
Because that’s what this space is really about—building in public, and not being afraid to do it while learning.
Let’s figure it out together.
And thanks to anyone who takes a minute to help a builder like me keep going.
Appreciate all the upvotes from @neoxian @enginewitty, and others I can't think of.
Nice! Thanks for getting this thing started; I've done some tinkering with a market trading bot before but not near as cool as what this would be. I'm looking forward to hashing it out x]
I'm kinda old to be learning to code. So I'm schooling myself and using all the resources I can to do this expeditiously. Beem is kind of where I'm stuck. I can't get the key verification, plus my servers crashed. Which set me back from what I had saved. It's a heartbreaker. I'm working on an auto FTP code to constantly save it from here on out.
Great move! What exactly was the issue with beem key verification? Were you getting any specific error?
The key error is likely that it's wanting to use the active key for the actual transaction but you only have the posting wif loaded. I haven't looked at the code, but if you have it loaded from the wallet, add both keys to the wallet, if you care calling it this way:
Hive(keys=[posting_key])
you should do itHive(keys=[posting_key, active_key])
Also, the beem library is dated, which is why I have taken upon myself to update it and get it caught up with the times under a rebrand. If you would like to use my current iteration, it's listed as hive-nectar and is mostly 1:1 compatible with beem, just
from nectar.hive import Hive
etc instead of beem. Feel free to reach out if you would like.I'm going to try using both keys to verify it's not what I've done. I will look into Hive-Nectar, I'm a rookie so I'm trying to establish this. I'll check it out later this evening or tomorrow after work.
Uploaded for the sport
Posted using LasseCash
Uploaded what?
oh sorry meant upvoted on LasseCash
Posted using LasseCash
Reblogged for visibility with hopes you get some more help as I would love this!
It would be nice if more of us had this information. I appreciate that.
Markdown syntax is largely the same as posts on Hive. Usually this will describe what it does, how to compile/run and configure it.
Looks like you just created one. You may want to include crash logs in your issue. Close them when the issue has been resolved.
They will make a fork of your repo, make their changes in a branch and submit a pull request for you to review and merge.
git pull
to fetch remote changes orgit push
to push any changes made locally. I personally use Github desktop to manage my repos.Thank you.