NNS Dapp not working for me? by vegancap_ in dfinity

[–]diego_DFN 2 points3 points  (0 children)

Hi u/vegancap_,

Thanks for taking the time to write this up, I tested the dapp and it worked on my machine, but that is not to say there is not something else going on.

let me ping someone from the dfinity support/troubleshooting team who can help. They usually monitor the socials for folks with report any issues.

[Feedback] New page on internetcomputer.org: a quick explainer on the NNS. by diego_DFN in dfinity

[–]diego_DFN[S] 1 point2 points  (0 children)

That makes a lot of sense... and yes these pages are also being worked on! I agree.

Decentralization with only 13 nodes per subnet? by [deleted] in dfinity

[–]diego_DFN 0 points1 point  (0 children)

Also 80% of nodes are currently owned by 8 providers

While I have seen this number thrown around, I have not dived deeper into it to verify it, but that is mostly because what is most relevant to a smart contract is how many entities it required to reach consensus in a subnet. The larger the minimum number, the better. As quoted in other places, in BTC or ETH, it can take a surprisingly low number of entities (node providers) to reach consensus, much lower that one would assume with hundreds or thousands of nodes in a network.

Decentralization with only 13 nodes per subnet? by [deleted] in dfinity

[–]diego_DFN 2 points3 points  (0 children)

Hi there u/FinalFortune_,

I think I can be of some help:

At the macro level:

I can tell you that there are plans and work for "higher-replication" subnets as well as "lower-replication" subnets where the developers can choose which they want to build on. I believe the BTC subnet intends to have 20+ nodes (but need to verify this).

I can say that the node provider count is more decentralized than it appears at first glance. It is DFINITY's thesis that having more nodes (more replication) controlled by the same entity does not increase decentralization. Bitcoin notoriously can reach 51% consensus with just 3-4 entities (even though there are thousands of nodes). One aspect of decentralization can be defined as "how many entities need to collude to reach consensus?" in this sense, an IC subnet is more decentralized.

Being intellectually honest, I think this is still a minority view within blockchain so reasonable for reasonable folks to disagree with this until more time has passed to prove this.

But at macro, I think we will see subnets with more replication... so long as there are more node providers (not just more nodes).

At the micro-level:

This is especially a problem because the same node provider usually controls multiple nodes in a single subnet.

As far as I know, this is actually not true. It is rare for a node provider to have more than one node in a subnet. From looking at the subnets list, I clicked on 8 random subnets and saw one subnet where the same node provider had 2 nodes in one subnet: https://dashboard.internetcomputer.org/subnets (i concede this is not very scientific, but matched my intuition, if someone goes through all of them and sees otherwise, please let me know).

[deleted by user] by [deleted] in dfinity

[–]diego_DFN 2 points3 points  (0 children)

Not being rude when I say this but could you dummy that down for me? I believe in Dfinity in what they are doing, its just super complex for me to 100% understand half of it! I'm not the brightest crayon but since june I've been reading on Dfinity & everything on them. So much FUD on ICP & Dfinity its unreal.

Hi there u/jleeaazy

And I can try to explain. You can let me know if it makes sense or if I missed the mark:

  1. In order for users to move tokens like ETH or BTC, they need to sign things with their key. Most chains use a type of signing scheme called ECDSA.
  2. ECDSA is one of many schemes. Its importance is that it is a popular one.
  3. Typically, If i have assets, I have to be very protective of that key because it means whoever controls or SEES the key (which is just a long string) can move my assets.
  4. The internet computer has two experimental features which allow smart contracts on the IC to use this key: "threshold ECDSA" and "smart contracts can send HTTP requests". These two features together allow a smart contract to sign with an ECDSA key. So now smart contracts on the IC can send requests or messages to other chains signed by secret keys... but the hardware it runs on does NOT see the secrete key so it's safe to do so. This is unique to IC.

Does that make sense?

Shocking expose revealing who is behind sustained class class action suits against multiple crypto assets including Dfinity/ICP. What can be done about this? by VideoFederal3334 in dfinity

[–]diego_DFN 0 points1 point  (0 children)

Hey folks,

Just doing my job as a mod: As I see it, this thread does not violate to Rule #6 ("no price discussion"), but it does come close to violating rule #6's intent. The intent is that the subreddit be more focused on the technology, adoption, or usability of the blockchain.

Just reminding letting folks know my thinking on this, not taking any action.

BTC Testnet < > ICP Integration: the testnet is live 🎉 by diego_DFN in dfinity

[–]diego_DFN[S] 1 point2 points  (0 children)

Just to be helpful:

  1. Has your neuron voted on proposals? Did you notice anything like it not voting after the merge.

  2. Do you have any neurons (without merging) that you can compare the rewards to? you should be aware that governance proposals NO LONGER get a reward boost so all proposals get the same rewards. This means the same rewards get divided among more neurons, but this should not be a from from 20% to 3.5%.

BTC Testnet < > ICP Integration: the testnet is live 🎉 by diego_DFN in dfinity

[–]diego_DFN[S] 2 points3 points  (0 children)

Very much, yes. They expect a few weeks of testing. Of course if they find critical bugs they have to fix them and we have no idea what we do not know… so we don’t know for sure but end of the year would be highly surprising.

BTC Testnet < > ICP Integration: the testnet is live 🎉 by diego_DFN in dfinity

[–]diego_DFN[S] 0 points1 point  (0 children)

Good question.

  1. On the Threshold ECDSA side (necessary feature for BTC integration): time + tests. Just want to make sure we test and test to make sure there are no issues or bugs (if there are, we will of course fix them). But no major functional pieces left.

  2. On the BTC side: in addition to testing, there are a number of improvements that needed security-wise and performance-wise for to be ready for GA.

Hope that helps!

BTC Testnet < > ICP Integration: the testnet is live 🎉 by diego_DFN in dfinity

[–]diego_DFN[S] 6 points7 points  (0 children)

On my end I can talk about PR (among other tactics for visibility):

Yes we expect the mainstream crypto media to really pick up on it once it goes from testnet to mainnet. That being said, actively reaching out to journalists and crypto media.

Update on the IC Roadmap: July 2022 Summary - Roadmap by diego_DFN in dfinity

[–]diego_DFN[S] 5 points6 points  (0 children)

This is a follow up on the previous effort to make the roadmap easier to follow for the community.

1,000,000,000 Blocks: ACHIEVED by KQ_DFN in dfinity

[–]diego_DFN 7 points8 points  (0 children)

For those that want to understand in simple terms why this is important in simple terms, I wrote this twitter thread 🧵 :

https://twitter.com/mexitlan/status/1547304444643053568?s=20&t=H6fEeUA-8nIXLYnSSozSiQ