I think it’s not your node, not your rules.
I agree. But we need to take into consideration that no-coiners want a seamless experience and can’t wait days to be able to send a transaction.
Until we have a good IBD solution, we need to make some trade-offs.
I don’t think Syrius should suggest any nodes, even if it is a barrier to accessibility.
The community can manage an external list of public nodes. I already have this list.
I do think it should. However if Syrius ends up being the equivalent of Bitcoin core wallet then some more user friendly ones can suggest nodes for the ones not willing to do more than 1 click.
Normies go for chrome extensions, how about we work to implement Layiids design and bring the chrome extension up to syrius standards while hardcoding a public node on it.
If ethereum wallets required everyone to run their own node or look for one on a forum, do we think they would have the same level of adoption they have today?
Maybe the nodes need to be approved by AZ. I plan to submit for the new my.hc1node.com.
I 100% agree with your comments. And for the people who are “qualified” to understand what you wrote they will use their own nodes. But for > 95% of the population they don’t want to sync a node and wait 24 - 48 hours.
So do we force them to run their own node and get frustrated and/or look for one that maybe a scammer provides? Or should we offer a solution that tries to balance adoption and some level of trust?
Imo we have 3 options:
EASY
MEDIUM
go-zenonHARD
Regarding medium and hard, I think the extension chain is more important than implementing either of these two solutions.
Regarding Easy, curious what others thinks. HC1 offers a public node today. I will ask for funding for it in AZ, which means the Pillars support it (f approved). Maybe AZ funding and community support is required for a node to be added to a list in Syrius.
I can make a sketch and we’ll see if we gather more support for this feature.
For example only approved nodes can be hardcoded into this list:
wss)<200ms)Idea: create a website like https://ethereumnodes.com/
Having public nodes easily accessible is a must for mass adoption imo, having a prompt when initially launching Syrius is the easiest way to achieve this - but the list needs to be dynamic and changeable without updating Syrius.
Then the question is do you also make it the default node choice vs embedded? And if so which public node?
There isn’t a reference wallet to compare to that I know of that has an embedded node so it’s hard to compare, but the IOTA firefly wallet is somewhat comparable in feel and use case and it just auto connects to a node
Imo we have a Metamask VS Bitcoin-core old school wallet kind of situation. The Metamask people will go for the simpliest way, the later will want to decide how to setup theirs. Keep Syrius for power users, for everyone else, plug a public node by default. Same as Metamask where you can change your rpcs.
We can compare this situation to Bitcoin.
There’s Bitcoin Core, which basically forces users to run nodes unless they’re aware of how to manually connect to one.
And then there’s Electrum wallet, which suggests connecting to someone else’s node, for convenience.
I prefer Syrius leans more towards the Bitcoin Core run-your-own-infra style of operation. Other Zenon wallets can make their own suggestions.
We can include a list of public nodes but there are elements of trust and management that we need to address.
I’m concerned this can lead to centralization; everyone will be connecting to 0x’s infra.
Is anyone else even trying to load-balance this demand?
(My public node is offline due to resource limitations)
We’ve built enough good rapport within the community to trust certain entities to run infra and/or honestly inform users.
For example, if zenon.org hosted a list of verified public nodes, new participants would likely trust those options over some random person’s suggestion on Telegram.
Provide funding for community to run public nodes?
Good points. Maybe I’m a little conflicted because I don’t have any problems connecting to my own nodes.
Back in the day, 2013ish… does anyone remember how btc nodes were handled? Were there public RPCs for people to use? I do remember needing the BTC core wallet and I synced up back then. I don’t remember spending the time looking for a public node.
I think we have a 12 - 24 month window to really start gaining adoption. Until we get more adoption I would be willing to do “things” that make adoption EZ.
Did anyone use the Terra Station wallet? Set aside it was Luna… The UI/UX was very good and easy. There was no mention of node, syncing, or any of that. You installed it, setup the Seed and it just worked. My business partner who does not know anything about how crypto works, could use it. He would not be able to sync syrius. No patience and/or ability to trouble shoot a single issue. In fact, he does not know what a node is, would not go to a site to find one, or enter telegram to ask about one. He represents 95% of crypto.
If we want adoption I think we need to consider some trade offs.
I am not aware of any pu lic rpc in 2013. It was the Bitcoin forks ride and we were all running btc forks nodes meaning - pretty much like Bitcoin-core - they were connecting to a bunch of IPs to initiate the sync and then sniffing for more nodes. ETH and Metamask brought the rpcs in, I think. If I remember correctly we had Electrum but it was not as used as it is today, nobody willing to trust a public node. Beside Electrum has a shit UX so it wasn’t attractive at all.
Offering a Syrius based power user experience and a normie one with built in rpcs by default (Bitcoin-core and Metamask) could do IF our Metamask equivalent is super giga simple. The average Joe will not bother learning. When our Joe will start understanding what is Zenon, he or she might even consider Syrius. But not at first.
I believe Syrius should be for everyone, no-coins and maxies alike: no-coiners will use public RPC community nodes and maxies will use the embedded full node.
For public nodes, we can implement a scoring algo for reliable nodes with some anonymization features (proxy/route requests, load balance & anonymize traffic, etc).
But everyone should be able to use the same wallet with a great UX suited for their own needs.
Listings like this is also a form of inbound marketing.
I have
go-zenon v0.0.6 = wss://my.hc1node.com:35998
go-zenon v0.0.5 = wss://secure.deeznnodez.com:35998
@sumamu @aliencoder @sol
Did a znn unwrap today.
After redeeming Unwrapped ZNN remained in unrecived transactions even though wallet was fully synced. Changing to hc1 node didnt help.
Restarted syrius, then it arrived.
Its a weird glitch. Never had this issue with receiving staking rewards
why wud this be any different?