My First HiveFest -- My HiveFest Presentation about Hive Layer 1 NFTs

in #hivefestlast year (edited)

HiveFest 2023 was an amazing experience. Rosarito was an amazing place to visit and @starkerz and @theycallmedan were exceptional hosts.

(Personal Note: My wife was able to join me on this trip to beautiful Rosarito, and this was the first ‘getaway’ she and I have taken together since our honeymoon 27 years ago. Watch the intro to my HiveFest presentation to hear why.)

My primary goal in attending HiveFest was to meet and dialogue with folks who are serious about Hive and serious about improving and expanding the Hive ecosystem.

I was by no means disappointed. I met and talked to many amazing people. Here is a non-exhaustive list of some of those with whom I had significant and meaningful conversations (in no particular order): @arcange, @brianoflondon, @sofiag, @grampo, @blocktrades, @alpha, @detlev, @khaleelkazi, @anomadsoul, @ura-soul, @crimsonclad, @neopch, @chrisrice, @nathansenn, @vaultec, @disregardfiat, @markegiles, @quekery, @smooms, @alessandrawhite, @intothewild, @eturnerx, @bitterirony, @jza, @evilpotatoes, @jeffjagoe, @lemony-cricket, @m31, and @jongolson and @taskmaster4450 (actually, jongo and taskmaster stood quietly behind me, with neo, peering in the window, over my shoulder, during my nerdy conversation over breakfast on Day 3 with vaultec, nathansenn, and markegiles; they listened intently but didn’t say a word). My apologies to anyone I might have failed to mention.


I began my HiveFest talk with a really quick 1- or 2-sentence overview of five different ways to improve the Hive ecosystem:

  • Suggested onboarding improvements
  • Need for a developer bootcamp
  • Increasing the voting power of manual curators without altering the balance of author / curator / stakeholder rewards
  • Improving decentralization by reducing the number of witness votes from 30 to 5
  • Creating a Hive Instant Notification system


The bulk of my talk centered on three novel use-cases for Hive Layer 1 NFTs, which are:

  • Hive Exclusionary Accounts

  • Hive HBD-Bond Accounts

  • True Hive Layer 1 NFTs


Scroll down to see all my slides from the presentation.

I will try to post some additional thoughts and details over the next few weeks to expand on some of the above topics.


You can view the livestream of my HiveFest talk here.

And here is an interview conducted after my presentation, with me, @crimsonclad, and @neopch.




Presentation Slides (@trostparadox, #HiveFest2023)


Slide1.PNG


Slide2.PNG


Slide3.PNG


Slide4.PNG


Slide5.PNG


Slide6.PNG


Slide7.PNG


Slide8.PNG


Slide9.PNG


Slide10.PNG


Slide11.PNG


Slide12.PNG


Slide13.PNG


Slide14.PNG


Slide15.PNG


Slide16.PNG


Slide17.PNG


Slide18.PNG


Slide19.PNG


Slide20.PNG


Slide21.PNG


Slide22.PNG


Posted Using LeoFinance Alpha

Sort:  

Hi @trostparadox, I did not find a good time to speak in depth with you at HiveFest so I'll take the opportunity here.

First, I thought you made a great point early in your presentation about what I would call "namespacing" and what you call a "prefix." I believe BitShares has this feature and I was surprised years ago when I found that there was no such protection on our chain. I'd love to see that implemented because right now, anyone could claim an account that looks very much like it is owned/operated by another. I think that if BitShares does it, there's no reason we couldn't. Obviously we would need to do this without affecting accounts which already exist, but I think that's as simple as doing a check once at the point of account creation. Something like: does the portion of the username before the dot match an existing user? If so, an additional signature from that account's owner (or active) key is required to create the account.

I would disagree strongly, however, with any protocol changes exempting stakeholders from curation duties. Our chain already enables this use case in a few ways. The easiest, and least damaging I think, is delegation to curation projects like @curangel. This allows stakeholders to entrust a group of humans to find and upvote quality content with their stake, and still receive a high percentage of the curation rewards. The curators are, of course, paid a fair rate for this transfer of responsibility, which I think is important.

I would disagree strongly, however, with any protocol changes exempting stakeholders from curation duties. Our chain already enables this use case in a few ways. The easiest, and least damaging I think, is delegation to curation projects like @curangel.

Thanks for the feedback.

If we are already allowing stakeholders to circumvent the curation process, why not make it so that it increases the influence of ALL manual curators rather than just delegation aggregators?

Delegating to @curangel (or similar delegation aggregators) simply creates a new (or more powerful) whale upvoter, whereas my solution would empower all manual curators with a greater upvote voice. I do not have a dog in this fight, btw. This is just my $0.02 suggestion on how to allow large stakeholders to willingly and openly contribute to decentralizing the manual curation process rather than further centralizing it.

Regardless of whether we agree or disagree, creating dialogue about ways to improve the ecosystem is my goal. Thanks for helping with that!

Regardless of whether we agree or disagree, creating dialogue about ways to improve the ecosystem is my goal. Thanks for helping with that!

And thanks very much for your reply! I agree that dialogue on these things is important. I recognise that not everyone has the same ideas and that's fine.

I do admire the goal of decentralisation and certainly, we do not want centralised curation. However, there are many projects to choose from, each with different criteria and rates of return. The space is open and there are no barriers to entry; a new curation project can be started by anyone. I believe this more than mitigates any concerns about centralisation; of course not everyone has to agree there.

If we are already allowing stakeholders to circumvent the curation process, why not make it so that it increases the influence of ALL manual curators rather than just delegation aggregators?

This is a great question. I actually do think it would be a mistake to distribute the increased voting power among the entire body of voters. Curation is more than just finding posts that seem good to us. It involves combating plagiarism, fraud, misinformation, and value extraction schemes, and that's hard work. Everyone can vote, but not everyone is a great curator, and I think the best thing most large stakeholders can do for the platform (and, therefore, themselves) is to delegate those responsibilities, not just to anyone, but to a team of professionals who have a good eye and know, frankly, "every trick in the book" by now.

I absolutely would not want to discourage anyone who actually wishes to curate by themselves with their own stake. But if a large stakeholder is not going to curate, they should at least be held responsible to delegate the responsibility to a party or parties they select. If they don't wish to do this, they can always forego curation rewards, but as they say, "there is no such thing as a free lunch."

We covered a lot of ground during our chats at the HiveFest!

Re: instant notifications

Waivio has a Telegram bot you can use:
https://t.me/WaivioNotificationsBot

Simply input your username(s), and you’ll get real-time alerts for replies, likes, follows, financial transactions, and more.

You can tailor the notification preferences for each account on Waivio. For instance, you can establish a minimum transfer limit, ensuring you aren't notified for minor deposits like 0.001 HIVE.

Plus, when you follow other users, you have the option to activate bell notifications to stay updated on their new posts.

IMG_5007.jpeg

Similar service exists for Discord users.

Thanks, @grampo. I enjoyed our multiple chats at HiveFest.

I will check out the Waivio notification system.

It sounds like it might accomplish something very similar to what we have been intending to implement, for non-encrypted messages. Ultimately, we would want to incorporate message encryption, using Hive memo keys.

As a side note, I noticed that Waivio requires HiveSigner instead of Hive Keychain. Do you have any plans to support logins with Hive Keychain and/or HiveAuth in the near future?

Most of our users are mobile, and signing in with Hive Keychain before HiveAuth was not practical. HiveAuth has made it much more user-friendly on smartphones. So, yes, we are planning to integrate HiveAuth.

For now, we advise users to use password managers to manage private keys on multiple devices.

https://www.waivio.com/object/ylr-waivio/page#6vcmab-tutorials/owg-best-practices-for-managing-hive-private-keys-on-multiple-devices

I would have loved to participate in Hive Fest but with work commitments and family to think about, I have never been able to do so but I hope in the future to have that opportunity as well.
Regarding your ideas to improve Hive I liked them very much and some I also found innovative like the True Hive NFTs.
!discovery 40
@tipu curate

https://leofinance.io/threads/rzc24-nftbbg/re-rzc24-nftbbg-2dzjv2h6m
The rewards earned on this comment will go directly to the people ( rzc24-nftbbg ) sharing the post on LeoThreads,LikeTu,dBuzz.

Great that you posted this here. I found your ideas very solid and I'm planing to go over them in a separate post of mine :)
Thanks for all the effort you put in.

Looking forward to hearing your thoughts!

Pleasure to finally meet you! Was great to chat at lunch and hear more of your story. Looking forward to see more of what you come up with at OSU. Go Cowboys! (OSU, not Dallas!)

It was a magical experience, good that you were able to go with your wife, share your honeymoon, it was surely special for both of you.

Glad to hear you were able to go. I strongly believe you spent quality time with people and enjoy moment there

!hiqvote
!PIZZA
!PGM

@quekery, the HiQ Smart Bot has recognized your request (1/3) but the mana is too low. Try again later.

As a consolation, @trostparadox gets !PIMP from @hiq.redaktion.

For further questions, check out https://hiq-hive.com or join our Discord. And don't forget to vote HiQs fucking Witness! 😻


Aw man @hiq.smartbot, you are out of PIMP to slap people.
Go Stake some more and increase your PIMP power.
(We will not send this error message for 24 hours).

pimp_logo


Read about some PIMP Shit or Look for the PIMP District

Sent 0.1 PGM - 0.1 LVL- 1 STARBITS - 0.05 DEC - 1 SBT - 0.1 THG - 0.000001 SQM - 0.1 BUDS - 0.01 WOO - 0.005 SCRAP tokens

remaining commands 0

BUY AND STAKE THE PGM TO SEND A LOT OF TOKENS!

The tokens that the command sends are: 0.1 PGM-0.1 LVL-0.1 THGAMING-0.05 DEC-15 SBT-1 STARBITS-[0.00000001 BTC (SWAP.BTC) only if you have 2500 PGM in stake or more ]

5000 PGM IN STAKE = 2x rewards!

image.png
Discord image.png

Support the curation account @ pgm-curator with a delegation 10 HP - 50 HP - 100 HP - 500 HP - 1000 HP

Get potential votes from @ pgm-curator by paying in PGM, here is a guide

I'm a bot, if you want a hand ask @ zottone444


PIZZA!

$PIZZA slices delivered:
@quekery(1/15) tipped @trostparadox


This post was shared and voted inside the discord by the curators team of discovery-it
Join our Community and follow our Curation Trail
Discovery-it is also a Witness, vote for us here
Delegate to us for passive income. Check our 80% fee-back Program