(general updates about subjects I enjoy, HIVE and things I am doing around this community)
The new reality
Still, very mild traffic of course and that's good for now. Buys me more time! ๐
Updates - Hive Engine Cloudflare protected API
On a previous post I have announced my official public RPC and P2P public addresses for my Hive Engine full-node. I am now adding the Full Node history node too. If you wish to add another node to your project that is hosted in New Zealand and protected by Cloudflare, then come definitely to have a look at these:
https://he.atexoras.com:2083/ (for RPC)
https://he.atexoras.com:2053/ (for P2P)
https://he.atexoras.com:8443/ (for API) - NEW Hive-Engine History!
Any feedback/problems, please contact me or check if there are any problems with these via the UpTimeRobot Monitor.
If you need more nodes, look at https://primersion.com/he-witnesses (you can click on them for extra details). As usual, if you are looking into running a node yourself, and you don't know where to start, drop by me on Discord or just ask below.
Using home equipment is VERY possible! ๐ - all you need is patience...
New Cloudflare protected 3Speak Network API
If you already found the news, 3Speak has reviewed the next stage of the network evolution with the ability to stake LARYNX and delegate them to others.
This allows people to (similar to how you vote for witnesses) support the nodes you see best protecting the network. At the same time, you will earn 0.015% SPK tokens, instead of the 0.010% you would win if only powered the LARYNX tokens. You can go to https://vue.dlux.io/me#spk to power up and delegate.
I have now moved the node I had to Cloudflare too at https://spkcc.atexoras.com:2087 that should give you something like this:
{
"result": {
"IPFSRate": 2000,
"MSHeld": {
"HBD": 41812,
"HIVE": 215502
},
"budgetRate": 2000,
"chaos": 0,
"currationRate": 2000,
"daoclaim": {
"ct": 0,
"m": "03",
"t": 0,
"v": 0
},
"delegationRate": 2000,
"dex_fee": "0.00513",
"dex_max": "93.20",
"dex_slope": "58.59",
"gov_threshhold": 26767478,
"hashLastIBlock": "QmT287BJEoimsdphFKy3MoH3jh6LGmz2bAkG88asv3daXv",
"icoPrice": 0,
"interestRate": 999999999999,
"lastBlock": "QmU3xwgzpy5GQ1oujFs4Ytc4CuADCKJMVBGM3o3iPTdyWy",
"lastIBlock": 67200700,
"liq_reward": 100,
"marketingRate": 208,
"maxBudget": 1000000000,
"movingWeight": 0,
"ms": {
"active_account_auths": {
"regardspk": 1,
"speak-scc": 1,
"tcmd-spkcc": 1
},
"active_threshold": 2,
"memo_key": "STM5GNM3jpjWh7Msts5Z37eM9UPfGwTMU7Ksats3RdKeRaP5SveR9",
"owner_key_auths": {
"STM6EUEaEywYoxpeVDX1fPDxrsyQLGTsgYf1LLDSHWwiKBdgRhGrx": 1,
"STM8P2DyNxDG5nuTWdtsifdTjhMRTirxEzXVnpxeXs5R3VbWTDyiF": 1,
"STM8ZZYUFkF8WqbFPh4xQLRGNUWsbJSK97cdPAvSBeLYKDoRqar1p": 1
},
"owner_threshold": 2,
"posting_account_auths": {
"regardspk": 1
},
"posting_threshold": 1
},
"multiSigCollateral": 3695140563,
"nodeRate": 516,
"outOnBlock": 0,
"safetyLimit": 340301289,
"savingsRate": 1000,
"spk_rate_ldel": "0.00015",
"spk_rate_lgov": "0.001",
"spk_rate_lpow": "0.0001",
"tokenSupply": 34796255389
},
"head_block": 67200822,
"behind": 18,
"node": "atexoras.witness",
"VERSION": "v1.1.2"
You can also monitor the network either using someone else's API (like this badass one from @hivetrending and the @pizza.witness) or learn how to read the API output yourself.
2022 Efforts and Activities
For me to keep checking on what I am doing, mostly. If some are not achieved, then I will move them to 2023. It's important to document what you do.
โ
Upgrade my router+firewall
โ
MongoDB light-node (using @atexoras, and mostly for experiments)
โ
Do a bit of work on a script I have for the "archiving" of snapshots for when things go very bad (now offloaded to external drives)
โ
(ongoing) HPUD 3x 1k HIVE delegations giveaways
โ
(ongoing) Occasionally go to people voting for LONG-stale witnesses and do a bit of voting awareness.
โ
Support at least one DHF project (with technical advice, review and/or direction) - I think I overachieved this one... currently on 3!!! but still managing๐
- let there be more ๐ฅ ๐
โ
Continue exploring SSL based traffic use-cases in order to make benefit from 3rd party tools/solutions like Cloudflare and minimize node exposure
โ
Add the Hive-Engine History node (https://he.atexoras.com:8443)
โ
IPv6 (light and full node now using IPv6 too, with IPv4 for backward compatibility)
๐ญ (maybe) revive the google drive snapshots service for light nodes (only makes sense if the number of users running light-nodes increases exponentially)
โ
Maintain Honeycomb type nodes as active as possible on DLUX, 3Speak and Ragnarok side-chains. Support them as possible.
๐โ๐จ Create an internal IPFS node to support Honeycomb side-chains (internally at first and primarily)
๐โ๐จ Explore ZFS (requires more memory) as a potential replacement for XFS
Also on my list, but initially longer-term things... and these get updated as I learn more from them and plan my time strategicaly!
๐โ๐จ ISP upgrade (pending install) ๐ฑ
๐โ๐จ More 128GB to 256GB ram for new projects! - THIS COSTS!!!! ๐คฌ
๐โ๐จ Newer CPUs (at least one new 16-core Zen3 by the end of 2022 is my objective, but in addition, a new host might be on the list for smaller stuff)
๐ฅ (probably not going to happen) Trying to create a new Storage Cluster (Ceph most likely) of (3-5) x nodes... but there are no resources... ๐ฃ This would be awesome for future growth and versatility - maybe a 2023 thing...
Happy face! ๐ค
๐ช Helping HIVE users... ๐
I will continue to help new ๐ users as much as I can... being that via the @atexoras.pub or the @atexoras token. But lately, I have been focusing more on projects that I either identify more with or where I see that my help will potentially improve things considerably.
But in general, anyone seeking genuine help through me will have 100% dedication... primarily free.
Disclaimer: I am not a Cyborg or Robot and therefore I might not be always available promptly, but I will eventually follow up with you. I also have a life. ๐
๐๏ธHIVE5's!
Have fun, good luck on all the gaming, learning, and when/if you are up to, teaching new things to newcomers, showing them how interesting is this place.
๐ค Follow me on Twitter
@forkyishere ๐ (@forykw dark side) is a character I created, emerged from Crimsonclad imagination ๐ while dwelling over the dark dungeons of Discord chat levels.
Follow for #news about the #HIVE #Blockchain, and other stuff. I sometimes get crazy with what happens around social media. I am following all HIVE users! No promises of behaviour. ๐
In addition, if you are looking for a nice place to either reach out, share or just have a great time, come along to @atexoras.pub gatherings. We welcome everyone on the blockchain.
๐ Vote for Witnesses
(โกVote) - Hive-Engine here - voting uses staked WORKERBEE
(โกVote) - HIVE here - voting uses staked HIVE
(โDelegate) - 3Speak Network - You win 0.015% SPK tokens if you delegate LARYNX to other nodes, as opposed to only 0.010% from your powered LARYNX!
@forykw is running ๐ @atexoras.witness on all the above ๐ช
๐ Hive Blockchain Games ๐ฎ
| Year | Title | Post link (๐4+โน๏ธnfo) |
|---|---|---|
| 2021 | The ecosystem is expanding! |  (credit @solymi) |
| 2020 | The power of having fun! |  (credit @doze) |
๐ณ Cryptocurrency Cards
| Crypto.com ๐๐๐ | Crypterium (forgot) | TenX (retired) | Revolut (pending) | Wirex (fuckdup) |
|---|---|---|---|---|
 |  |  |  |  |
by 
Posted Using LeoFinance Beta
I delegated my larynx to your node, and I will do so with my alternate accounts that have larynx later today (memo to myself: @splinternews use your larynx)
I think after so much work you did -the checklist is impressive- you deserve a cold !BEER
I saw something like multisigescrow and then a number.
Is there a multisig solution for handling single hive accounts?
Appreciated. =)
There is multisig in HIVE, yes, but not many use it. I have tried it out on the Pub account actually. =) But have not finished what I was planning yet. It's has some tricks =)
It's not the same methodology as in WAX/EOS if you are used to that model. But it's effectively multisig. And its used on here to control the funds that are used for bids in the DEX as collateral. Basically everyone locking LARYNX into governance has a percentage of that, that can be used for BIDs via the multisig keys that keep also changing depending on a number of factors.
Currently (at the time of writing), this much HBD and HIVE are still "available" for bids (need to divide by 1000 to get real numbers):
"MSHeld": {
"HBD": 45193,
"HIVE": 244518
So, I put a bid in for selling XXXX LARYNX for 45HBD, almost all HBD will be used (locked) to create the bid. Then when someone pays the actual 45 HBD, it get's unlocked and returns to the pool. Etc...
The model of this side-chain is quite interesting to me. We have a lot to learn from using these different ways of maintain consensus and via decentralized ways, explore the nature of how resilient these methods are.
For me, a real please on dwelling into this. If I just could have unlimited time!!! ๐
Anyhow, hope it added something new here =)
!PIMP
You must be killin' it out here!
@forykw just slapped you with 1.000 PIMP, @solymi.
You earned 1.000 PIMP for the strong hand.
They're getting a workout and slapped 1/1 possible people today.
Read about some PIMP Shit or Look for the PIMP District
So would there be a way to have a hive account only sending funds if certain accounts sign the tx? Is this possible on layer 1? I really would love to implement this with our guild account @acolytesofhelio
Yep, that's the way multisig works.
The question here, is how that is processed. And on EOS derivates each transaction can be broadcasted individually until the requirement is met. On HIVE, if I am not mistaken, the current implementation only allows a full broadcast to complete the requirement. Meaning that until all signatures are put into a single broadcast, it will not validate the multisig.
Hence there are 2 options:
The first method is obviously "central" and you can't easily to do an ALL TIME working thing... the later could be automated but its not a very efficient process (may require many broadcasts if there are many signatures).
I know @stoodkev has a different implementation previously shared. And he has some willingness to work on it on the future (to even someone like me would love to participate even knowing it would be out of my comfort zone). =) Hopefully this will become as easy as it can... for anyone to use.
Multisig will be a necessary mechanism for when HIVE is worth 1000$ =) not just, but otherwise big companies will be very reluctant to use HIVE if not offered more protection than just a single key.
It would need a userfriendly frontend where involved accounts get notified that the tx needs their signature.
@forykw! The Hive.Pizza team manually curated this post.
PIZZA Holders sent $PIZZA tips in this post's comments:
@torran(9/10) tipped @forykw (x1)
Join us in Discord!
View or trade
BEER.Hey @forykw, here is a little bit of
BEERfrom @solymi for you. Enjoy it!If you like BEER and want to support us please consider voting @louis.witness on HIVE and on HIVE Engine.
!PGM
!PIZZA
!BEER
View or trade
BEER.Hey @torran, here is a little bit of
BEERfrom @forykw for you. Enjoy it!Did you know that you can use BEER at dCity game to **buy dCity NFT cards** to rule the world.