Blog
photo_2019-08-31_14-18-45

Sentivate AMA with Tom Marchi hosted by Crypto^^Nation

Sentivate is actually two networks with opposite topologies. The first and primary network we call the Universal Web. The UW is centralized focused but can make use of and benefit from decentralized additions. The easiest example is a P2PCDN for typical Universal Web Apps. The second network is Viat that is our native cryptocurrency. Viat is decentralized focused but there is an opt in for many of the centralized features. Most of the centralized features are geared toward everyday users and businesses for security and speed. Two examples being Wallet security and instant transactions all of which are essentially provided by centralized services. That’s Sentivate in a nutshell.

SNTVT is an ERC-20 and Viat is our native cryptocurrency on its own blockchain. We are leaving the Etherum network.

Adoption:
Love this, I’ll try to summarize for the sake of time. B2B, B2C, and B2G in a nutshell. The first step is we are re-releasing apps exclusively on the Sentivate network that have a history of use and success.

How Sentivate will solve  universal data congestion issues?

This is related to what we call the bandwidth crisis and has be spoken about for some time now even in the news. The Government here made initial moves to allow companies to deal with the issue from a less technical perspective which is removing net neutrality regulations. Essentially to deal with this issue quickly and broadly from an NSP’s perspective is to create speed lines and data prioritization. This acts as a form of effective network congestion which will buy us a good amount of time but I fear will create classes among Internet users. None the less it is an effective response to a very complex highly technical issue. We approach it at its core. Which is the Web relies on many out dated technologies that aren’t forward thinking and we tend to get locked up into these protocols and methodologies. There are three main technologies that solve this issue. The first is our DIS. The Domain Information System is similar to the DNS of today except that it supports more features like GEO Location based results and can make use of a decentralized network that can serve out requests on it’s behalf. Another core benefit of it is that it returns a cryptographic certificate instead of just your traditional routing information. This allows us to have a decentralized DIS in addition to a centralized one. As now if a decentralized node responds with a certificate it can be verified via its signature. Thus we rely on math as the foundation for trust in that delivery model. Today DNS simply returns routing information and in some cases isn’t encrypted and we run into many security related issues for users that we tend to see on the news. For example rouge DNS servers in Iran targeting US citizens abroad. Essentially pulling off an elaborate man in the middle attack. If they attempted to do this using our DIS it would fail because the signature provided by them with the malformed data will prove to be incorrect and thus the clients would never send you to the place which the DNS is telling you to go. On top of this issue and more related to the bandwidth crisis is how delivering the certificate via the DIS changes the dynamic of the connection handshake to services. UDSP is designed with the DIS in mind and vice versa. We can see this by UDSP taking advantage of pulling the certificate from the DIS and automatically capable of pulling of a 0-RTT connection without ever having to of visited the site before unlike how the web works today. To establish a 0-RTT connection today, (first off based on current security recommendations and for DDOS protection it’s advised against even for the most recent versions of HTTP), you must first visit the site and do a traditional HTTPS handshake to get the certificate and then if enabled will be able to do the 0-RTT next go around if the certificate is still valid and or still cached/saved in your client. Another key point here is that when you make this initial handshake with UDSP you can actually auto signup/login the user. Which means that the data transport protocol itself is designed to take advantage of this 0-RTT handshake by also doubling as a single-sign on for services. Effectively this makes your identity certificate aka your profile for the Universal Web a single sign on for the entire Universal Web. Side note is that there are Packet Puzzles which if enabled can offset DDOS attacks from traditional botnets we suggest reading the Minimalt papers regarding this approach as they have great insight on this and we mention that white paper constantly in our work. Onto UDSP. UDSP is a custom UDP protocol with a smart reliability algorithm. Which means that it’s less chatty than HTTP meaning less packets are sent back and forth and thus your downloads are faster. If like most services you also send JSON to the client we support MSGPack now with our recent update out of the box. Which means even smaller and faster packets before compression. Onto hApps. hApps are designed to act as applications that build themselves as the app is used. Think of a bridge that builds itself as you walk across.

Point being only required assets at the moment are sent over the wire. Only assets required at that given moment that are needed to render the next state. All those assets are streamed of a bi-directional real-time UDSP connection. That means for the life cycle of the application you have access to the same connection for all assets and real-time data. For those developers out there think QUIC meets Websockets to summarize it. At the end of this day all of this means dramatically less requests and dramatically less data sent across networks. The US Gov has already responded to this issue along with business communities. Without addressing the core issues the web will become more and more expensive, faster speeds will become less and less common, and bandwidth will become a scarcity. Large companies like Google has quietly installed QUIC into chrome browsers without everyday users knowing to address this issue with HTTP. Sadly the best response they have is HTTP3 which will certainly help the problem but by an insignificant percentage and essentially just buying us time during this rat race.

Hopefully that covers a majority of it. I can go more in-depth on any of the above topics if you want to get specific. I tried to hit on all major pain points.

Web 3.0 we are outspoken and against. From a technical perspective this is unrealistic. Basic physics it shows us regardless of how convoluted you make a consensus algorithm the data must travel to more nodes as for a consensus to form on the data. Meaning it must travel longer distances and requires additional computation before it becomes processed and propagated across the network and of course becomes a part of the blockchain in question. For hApps you are not limited to the networks capabilities and you are not forcing users to pay for requests. It’s very silly to suggest that users must pay for a request just to send a message to their grandmother on a blockchain based messaging app an example is chat apps that rely on BSV. Your daily actions on the web will not all have a cost to it meaning users pay way more out of pocket to do every day things. The data access and delivery is much slower than say a large network like Akamai for video or Cloudflare for a CDN. More importantly if we ever adopted a Web 3.0 Decentralized and blockchain based web it would crash the global economy the moment we switched to it. High speed trading happens in Ms if you slow that down you are talking about bringing the global economy to a crawl. Amazon said every 100ms of delay is 1% loss in profits and that’s a lot of money for Amazon that’s millions. This % has grown to 7% by some estimates put out by I believe Akamai (we site sources on our site regarding these). If we ever made a switch to such a limiting network design it would cost companies those who employ the world over absurd amounts of capital and thus killing the economy and putting thousands around the globe out of work. If we introduce a consensus algorithm to process basic purchases or PayPal transfers which are near instant we are talking about slowing down the vehicle that money uses to move from server to server. We detail out on our site much of our issues with Web 3.0 in detail that link can be found here (https://sentivate.com/info/the-issues/the-decentralized-web-isnt-the-answer/).

Onto UDSP now. Universal Data Stream Protocol is just that. It’s a bi-directional real time protocol designed to stream over data over the life cycle of it’s use. It can be used for straight upload and download but it more designed with the real-time web and future demands in mind. It’s a custom UDP based protocol and is a sort of mash between QUIC, HTTP, and Websockets for the devs out there. The web could easily adopt UDSP if it so chose to. Much like how google quietly installed QUIC support on its servers and browsers. If the tech community wanted to support it they could simply push out support for it. However, the best case scenario and the real benefit comes from not just adopting UDSP for the Web but also Identity certificates, DIS, and decentralized capabilities to further enhance it.

FASTER, SAFER, & MORE SCALABLE than any other solely centralized or decentralized web. Why can you say that ? i know a project like you (Brave , $bat ) ,what is your differences ? @TomMarchi

We are the exact opposite of Brave. We don’t even use HTTP nor do we use DNS. It’s a totally different Web with an entirely different domain system and much stricter rules. Brave wouldn’t be able to browser the Universal Web unless they incorporate our technology to browser and entirely different web. We provide support for browsing HTTPS sites within our browser however our only concern are UW:// based sites. You can confirm this by looking at our source code and seeing how we don’t use HTTP for UW sites and require totally different certificates to even establish a UDSP connection. Brave which uses HTTP to browse the web of today is based on TCP. If you browser a UW site it’s using UDSP and which is UDP based. You seem to be confused with HTTP sites and UW sites, they are two different things. HTTP sites do not run on the UW. We simply support HTTPS in our browser so folks can browser both the World Wide Web and the Universal Web.

How successful implementation of UDSP would benefit the Entire market?

It would drastically speed up the economy, save consumers money, save business money, improve the bottom line based on the 1% profit loss with Amazon.

How would you introduce the concept to people who have not heard of sentivate Network before?

I like to start with the way the networks are built personally. I’m a developer the businesses and entities I speak with tend to be higher level folks with a good knowledge set to communicate with.

All market related questions we will not answer. We will take no part in what we see as unethical behavior that many projects do. Everyone is allowed to speculate and we will not interfere in anything related to the market including exchanges. If we suspect an exchange leaks we may halt the process on it. We never release info ahead of time. We do however release info in a select order mainly our Discord first then Telegram then Twitter. As well as other crypto Telegram communities.

All world say’s Web 3.0 is a magic globe . which issue you see in that and how your platform better than web 3.0 – We have a great write up on this check out this as it’s a long answer – also check out my above comment regarding Web 3.0 https://sentivate.com/info/the-issues/the-decentralized-web-isnt-the-answer/

To be different and unique What initial replacements & additions will be introduced regarding Sentivate’s Universal Web?

DIS, UDSP, Cryptocurrency integration via packet puzzles/Certificates also act as Viat wallets, Identity Certificates, and hApps just to name a few.

Can you explain why sentivate believe that neutrality is evil ?

Many people think that net neutrality is a good thing – A good read for this to start is here https://sentivate.com/info/the-issues/the-web-is-running-out-of-bandwidth/ (https://sentivate.com/info/the-issues/the-web-is-running-out-of-bandwidth/) –
In a nut shell it means that the companies that would have to pay didn’t want to so they tried to make it a political stance when in reality it’s a technical issue. If we did not remove those regulations we would face a serious slow down to the entire Web.

Have you talked about it with any of the big internet companies (either for information exchange or direct collaboration)?

Yes, we have mentioned their name before but at this time it’s not appropriate to disclose who. As we will be approaching them again seeking a partnership/deal.

Regarding the happs: if for certain services the use of username and password will not be necessary, then specifically what would I need in the future to access my accounts?

Identity certificates which you can carry around with you. Ephemeral certificates can be taken anywhere and you can assign ones to specific services. All ephemeral certificates have a Master certificate which is sort of like your backup key in case of loss or ephemeral certificates being slightly compromised. For average users we call this profiles and we keep things much more simple for average users.

Where do you and the Sentivate Network team see the world of blockchain being in years to come, and how will Sentivate change the landscape of the cryptocurrency space in years to come?

We will see a large die off of almost all Web 3.0 projects. As they will fail at adoption and cost far too much money for the average consumer. Possible exploits found in privacy focused crypto currencies. Gov agencies investigating and possible destabilizing certain cryptos. Large brute force attacks on wallets. QC using shor’s algorithm compromises entire blockchains and crypto currencies. CC becoming a new asset class in addition to traditional stocks for all major companies. CC giving rise to a new Web which has it integrated deep into the core technologies of it.

When does team/advisors token unlocking start?

We have decided that the team lock up is until far after the Viat swap occurs. As the community expressed this as their wishes and we listened.

What are your next steps (2020 if you want) to the sentivate project?

Launching the centralized portions of the Universal Web opening the flood gates up for hApp development and testing. Along with our own series of applications that we are re-releasing exclusively on the Universal Web.

UDSP is based on UDP but the protocols function entirely differently in respect to the connection and the transporting of data. UDSP has a reliability algorithm, chunking algorithm, session support, real-time capabilities, login, signup, and the most important bit UDSP is a real-time bi-directional stream. UDP has none of those as UDP can be looked at as a basic network protocol which makes it perfect to build data transport protocols on instead of TCP. TCP has many things already built in and thus we lose control and can’t innovate not even close enough to fix this issues. As TCP is at the heart of HTTP and is its main pain point. We don’t support Web 3.0 we speak out against it. Please check out this write up on it https://sentivate.com/info/the-issues/the-decentralized-web-isnt-the-answer/ – Build an Alt-Web that is prepared to go beyond the stars and tackle many of the current and upcoming issues on the web and eventually the Internet.

Leave a Reply