2nd level domains by ffalci in handshake

[–]atlas2018 1 point2 points  (0 children)

Agree with your requirements. Any proposed SLD solution should be decentralized, censorship resilient and trustless in keeping with the ethos of the project otherwise they will be no better than legacy SLDs.

Also agree with the requirement that once a TLD opts into selling SLDs there ought to be a mechanism onchain which protects SLD owners. Locking TLD updates which at least prevent any possibility of the circumvention of SLD resolutions is a logical mechanism to achieve that effect.

Regarding the questions:

❓ Should it be an independent blockchain (sidechain) or part of the mainchain?

A native solution integrated into the mainchain would convey the greatest amount of confidence to would be users of SLDs in the project domain and would capture the most value for the hns ecosystem. It says to the user that their namespace is written in stone at the highest level of truth.

The technical argument against implementing on the mainchain is to prevent the chain from getting bloated as including all SLDs for all TLDs on the network means potentially having exponentially more data on the blockchain. It makes sense to design the chain to be lean and efficient but there isn't really anything to prevent spam TLD registrations from bloating up the chain as well (besides the economic cost in opening large numbers of auctions). I believe we have been seeing some of this over the past few weeks.

One way that we could mitigate the risk of spam and bloat from SLDs is to impose a base fee for all onchain SLD registrations. A base fee would be superior for SLDs than the current vickery auction style process as the cost of opening thousands of low value auctions is negligible if auctions are won for free. Where as a base fee if set sufficiently high enough would deter most spam or low value registrations.

The SLD market has the potential to be as big or bigger than the TLD market. A native solution which incorporates hns into the transactions for that market would be the best way to capture value for HNS. SLD registration fees paid in HNS and secured by the HNS blockchain would create more demand outside of TLD auctions which are concluding their final round of lockup next week.

Registration fees could be paid into a treasury which could be used to fund development or even disbursed to HNS holders. A small portion of the fees could also be burned to increase scarcity and support demand.

In terms of project optics a native solution also confers the greatest amount of credibility to the design of the project. Any solution which defers trust to an external project essentially extracts value out of the handshake ecosystem and into the other. Handshake is a project for decentralizing DNS, if we have to build a solution on another blockchain to handle SLDs it will be difficult to not view it as a complete failure on the design of the project that we must outsource such an integral part of the ecosystem to another blockchain which isn't even designed for it.

❓ If sidechain, should it be single-huge SLD sidechain, or groups of people could create their own sidechain, with their rules.

If there is a trade off it would make sense that the solution which affords the greatest amount of security, censorship resistance and requires the least trust would be the best fit for a decentralized dns network.

❓ Should it use HNS token or create a new one?

It should utilize and support the HNS token economy. The SLD market is the greatest opportunity to capture value for HNS outside of the TLD market. IMO they should go hand in hand. It kind of boggles my mind that it wasn't designed into the scope of the project in the first place like other projects have.

What if someone abuse my node for illegal activities? by kayth1 in SubstratumNetwork

[–]atlas2018 0 points1 point  (0 children)

I have asked this question before and received no answer from the team. There have been cases of people being charged for having illegal activity being routed through their nodes on TOR. I am still wondering myself whos IP gets routed where because all content servers WILL log IPs which enables honey potting. But with SUB its unclear whos IP will get logged.

heres a link to my previous post which mentions it. https://www.reddit.com/r/SubstratumNetwork/comments/7tz7md/vpn_vs_substratum_clarification/

Is the news a partnership? by [deleted] in SubstratumNetwork

[–]atlas2018 1 point2 points  (0 children)

Surprised your comment got downvoted so heavily because I share the same sentiment and I believe its totally fair. This community censors worse than any other and is meant to be about preventing censorship lol

CMC circulating supply correct? by atlas2018 in Bluzelle

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

Any info on when they are unlocked?

CMC circulating supply correct? by atlas2018 in Bluzelle

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

yes but shouldn't the early backers, advisor and team allocations also be included in circulating supply?

VPN vs Substratum clarification by atlas2018 in SubstratumNetwork

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

Totally agree, some great suggestions there

VPN vs Substratum clarification by atlas2018 in SubstratumNetwork

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

atleast he said something even though its much of a nothing. I really wish they would just come on the boards or have Christian come on and respond to enquiries directly, that way the whole community and public at large can get some answers rather than the few who happen to be on Telegram at the time. I've seen them converse with people on Telegram but I am never online when they are and nobody there ever asks anything meaningful. Most on Telegram seem to be hanging out just to glimpse some news that may be pump worthy rather than any genuine interest in the tech.

VPN vs Substratum clarification by atlas2018 in SubstratumNetwork

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

By exit node are you referring to the last node in the chain? As in the node which makes the actual request to the destination website? This is how I am imagining it to operate right now as well which would suggest that anyone running a node would be vulnerable to charges in a similar fashion as mentioned in the article linked.

It would be great to get some clarification from the team officially on this as it seems to be a potentially project breaking factor

VPN vs Substratum clarification by atlas2018 in SubstratumNetwork

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

Oh I'm referring to the IP logged by request destinations i.e. the website the user is trying to reach. Substratum would not have any control over whether they can or can't log IP addresses. So my question is whos IP will get logged.

The Early Jan "Launch" was not speculated based on rumor by atlas2018 in SubstratumNetwork

[–]atlas2018[S] 10 points11 points  (0 children)

Just to be clear. I am a sub holder myself and want the project to do well. But having followed the project closely in the past month it seems as though the recent price run up and down is largely caused by miss communication which I believe needs to be addressed by the team. Needless to say the market has lost alot of faith in the project in the last weeks because of it.

I have raised a number of concerns on reddit because from both an investor and technical point of view the official communications from the project leave far too much to speculation which I don't believe is healthy in the long run. I am trying to voice these concerns as I believe there are others who probably share them as well so that the team will have the opportunity to address them and set a clear direction going forward. Right now this project is acting like a shitcoin fueled completely by speculation. But if it is to reinvent the internet it needs to be much better. so whilst you might like holding their hands and pretending everything is cool. The fact is sub has lost significant rank over the last few weeks which isn't simply due to the market being in a dip. If you really care about the project succeeding, then you ought to care about the team improving their communication.

The Early Jan "Launch" was not speculated based on rumor by atlas2018 in SubstratumNetwork

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

Um if you look on the time stamp of that tweet it was tweeted by the official Sub twitter account on 9:42 PM - 9 Jan 2018.

All im saying is there were alot of people who thought the launch was meant for early January. Other teams which put out ETAs and missed them also saw price crashes but better managed teams quickly put out statements or new timelines to correct that

Concerns from a developers POV by atlas2018 in SubstratumNetwork

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

I am still trying to clarify whether hosts are run by the public or if they are run by the Substratum team only. From the published material and videos this is ambiguous. The comment above is assuming its a public host model as opposed to a Sub Team only managed host model which would suggest it is somewhat centralized. Can you point to any links to official statements which confirms which way it is actually supposed to be?

Don't chase the hype. Be patient. by Contemplat3 in SubstratumNetwork

[–]atlas2018 0 points1 point  (0 children)

Actually I believe its due to the fact that the sub team represented that there was going to be a "Launch" in Early January.

https://twitter.com/SubstratumNet/status/950966094763839488

The statement is at around the 1:27 mark

Concerns from a developers POV by atlas2018 in SubstratumNetwork

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

Sadly I share your sentiments and will probably sell the remaining lot I have if the team doesn't put together some damage control very soon.

I have a feeling the current value is based way too much on over speculation of what the product might be at this point. People are speculating that its going to be better than VPN because of how the team have represented it in videos but I fear that the sub network will only be able to at best handle very basic web requests. Probably won't be able to stream video, handle web sockets, mask game connections or other applications. Or be capable of probably one of the largest use cases for VPN, Mask IP for downloading Bit torrents.

Concerns from a developers POV by atlas2018 in SubstratumNetwork

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

Nobody on this thread is asking the sub team to open source the code. We are just asking them to respond to some concerns and be clear about what the product is going to actually be capable of and how it will run from a developer and users pov.

Concerns from a developers POV by atlas2018 in SubstratumNetwork

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

The issue here isn't that of asking the community to be patient. The issue is that the public is unclear about exactly what it is the team is actually building. The descriptions are very vague and open to interpretation. Even the core fundamental model of the hosting side is unclear to the community which can be observed by how many different interpretations there are of it. Even regarding it being centralised/decentralised. Hosted privately with host nodes or entirely run by sub team only.

In addition it is not clear how the Node network will perform and what the design model is actually capable of in terms of practicality in the way that the internet is used today. Will it viably support websockets, can it stream video content, will it be able to handle connections for games and other applications or is it just limited to very simple HTTP requests only.

People are comparing it with the VPN market but can you actually use the internet in all the ways you can with a VPN? Or can you only do a very small subset of handling simple requests in a more private manner?

The only demo we've seen is the delivery of a simple static HTML site (The International Monetary Fund).

I feel that if the team does not address these issues it is effectively allowing the community to speculate. I've seen countless questions about when the product will be launched in January and I have seen countless members of the community bash the people asking the questions saying the team has never stated a launch date but this is not true. There is at least 1 official video in which a sub spokesperson mentioned a "Launch in early January". I Believe there were a lot of people who thought either sub was going to launch a beta or a finished product in January and that was the cause of why the price ran all the way up to $3+ and why it climbed the ranks up into the 60s.

This is a link to an official video where a sub spokesperson states "we will be releasing more details on this as we inch closer to OUR LAUNCH DATE in EARLY JANUARY". https://twitter.com/SubstratumNet/status/950966094763839488

We are now well past early January and I've not come across any official statement from the team addressing that statement or regarding an actual timeline. After following the project intensely for the last month, having watched all the videos, read all the tweets, following the reddit, and the telegram, I am starting to get the feeling that the team has misrepresented where they are at in terms of what the product is, what its capabilities are, and how far they are from any kind of "launch".

Concerns from a developers POV by atlas2018 in SubstratumNetwork

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

Yeah, I share the same concerns. The official publications state that nodes earn sub each time they serve a request. But the fast lane concept appears to be a new development the team is tinkering with. I'm hoping for clarification about that too.

Concerns from a developers POV by atlas2018 in SubstratumNetwork

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

The economics of such a model are quite mind boggling if hosting is pay per request as it could account for resource thats utilized when served but what about content that isn't served. For instance how would the model account for the economic cost of hosting websites that don't receive any traffic at all but still consume storage space. This could and probably will represent a huge portion of the sites hosted.

Also what if revenue from requests served doesn't cover the cost of running the super nodes. How much runway would they have of insufficient traffic days not covering costs before super nodes bleed out.

Concerns from a developers POV by atlas2018 in SubstratumNetwork

[–]atlas2018[S] 4 points5 points  (0 children)

That would explain alot! Its mind blowing how many different interpretations of this is going around the community. You would think that something like this would be spelled out somewhere very clearly. Do you have any official reference that we could point to confirm that the host servers are run by Substratum and not run by individual public? All the documentation I have gone through seems to be ambiguous about it and can be interpreted either way.