I've been spending my workstation time trying to get a "delegate available" button to work, but JS isn't my strongest language so the button isn't opening keychain yet and the logs are telling

Great tips, save what you can, when you can!

At the moment it isn't. Cleaning up the code and making it available is on the list of things to do though. Most of the stuff I write for hive, depends on other stuff I've written and is already feeding

SPORTS is running 2 proposal systems. One that I wrote a couple years ago, and one that the hive engine team wrote. The hive-engine one allows control of a fund of SPORTS, people can propose whatever,

fixed the problem that had my proposal stuck, and found your problem. #sportsproposals you used #sportsproposal, edit your post, add #sportsproposals, notify me, and we should get this to work

It's one way, it may go back to 2 way someday. But for now it's delegate in to gain, swap out to get tokens.

Continue to gather support for your idea, I'll have it fixed before you finish gathering the required support, and if I don't finish before you have it, I'll move it up the list. EDIT: But yeah I'll try

Oh I am certainly able, and even willing, I'm just saying it's lower down on my list of things to do

I was able to get the 2 options for my proposal, but the system has yet to notify that the proposal has failed to pass. The whole thing was, and is highly experimental, and temperamental. But I don't think

It is designed to be one way to feed delegation payouts. The delegations feed swap. It goes full circle.

ALIVE has been chosen as the next token to be added. If I had all the facts when I was initially setting up pools, ALIVE would have been one of the first added. Are there any facts or information I should

ALIVE wins as the next to be added

ALIVE will be coming, too many users are using it to not add it. It's just a matter of if it's next, or the one after.

The possibility of a pump or pumps is pretty good with CINE.

I still think the 2 would need to be seperated, as @dhedge would need earned BEE to feed swaps. But you have given me an idea. I think I'll hold off on the workerbee pool for now, and add a workerbee section

The archonbank workerbee pool splits up earned bee between its users. This would pay its users in DHEDGE no matter how good or bad the days mining results were. Due to the different nature of payouts,

Yes, it's on its way out. All holdings were either transfered to swap or drips.

It does, but I haven't been in there for quite a while now. I had my fob taken that grants access to things like that. I try to stay out here now, discord leads to back room deals, and extra coding work.

@dhedge.bonus stores a portion of incoming swaps, then takes a portion of that DHEDGE balance and splits it up between delegation pools, drips, and burning it to @null every hour. This slowly feeds delegation

if you sent it before I fixed the nodes, you will need to send another 100K with that memo again. It would have picked up the transaction, added it's txid to the list of processed txids, then failed to