Sentivate is a revolutionary advancement in the internet architecture. Sentivate has a hybrid topology consisting of interconnected centralized and decentralized systems, and designed to go beyond the capabilities that any solely centralized or decentralized network could offer. Sentivate has the ability to operate in a decentralized or centralized topology, if the need ever arose, giving it a unique dynamic topology.
Sentivate is designed to be a realistic and viable replacement for the increasingly sluggish Web we have today.
Hey Tom. I appreciate you taking the time to join me today. Can you tell us more about yourself and Sentivate?
Thanks for having me Uzi. I’ll keep the bit about myself short as I prefer the focus to be on the work. I’m a builder at heart, have a constant need to create, and I continually strive for perfection in my work. I have been developing longer than half my life span. I have built a plethora of apps in different subject matters such as: genetic applications, mobile apps, neuromorphic front/back-ends, utility libraries, websites, real-time apps, social media automation, social networks, benchmarking software, security, frameworks, high speed trading apps, CSS design frameworks, RFID solutions, media applications, torrent streaming, IT, modified browsers, and GUI designs.
Enough of me though and onto Sentivate, The Universal Web, and Viat its native cryptocurrency. The Sentivate Network is effectively two separate networks that are interoperable and have the opposite balance in topology.
The first and most important network is the Universal Web. The UW is designed to be a realistic, viable, and true replacement for the web we have today. The UW is centralized focused but can be enhanced by decentralized components. The UW brings a series of replacements for the core software technologies that drive the web such as HTTP & DNS. There are new technologies that are introduced into the mix like the Identity System & Viat integration which are missing from the web.
The second network is Viat and it’s decentralized focused and can be, if opted-in, by centralized systems. This allows Viat to offer things like wallet security & instant transactions. Viat offers this without doing what other cryptocurrencies do like freezing wallets without direct permission to do so. Wallets that have these features enabled are all publicly visible allowing consumers and businesses to operate with some level of confidence and trust not present in other cryptos.
How did you get your first break into the world of cryptocurrency?
Very early on I saw BTC on GitHub and that peaked my initial interest. From there I got involved in mining with friends and slowly after trading. Eventually I wrote a Binance and leverage trading bot. It was as high speed as possible within the context of API limits. One issue the bots ran into is that it couldn’t trade as fast as it wanted to because of an API or network rate limitations. This over time was adjusted to more of an opportunistic trading bot that took in more details. We’ll be releasing a trading bot or code for it on the Sentivate Network exclusively at some point. We had experimentations and prototypes of blockchain related tech for purely research and development purposes. The experiments were designed to prototype ideas quickly and see how they could play out on a larger network.
What does a normal day in your life look like working with Sentivate?
The first thing is to address the team, messages, and community. A quarter of the day is all about communication and outreach. My messages on Telegram are filled to the top every morning so the best place to reach me and core team members is Discord. Discord is our main community hub and has excellent spam prevention mechanisms out of the box.
The rest of the day is all about code and standards discussion. Since we are building a new Web from scratch a lot of our discussions are focused around future proof web standards. Prototyping and code are a majority of the day. It’s safe to say I code a lot and practice what is called extreme programming. Essentially I delete what I made and re-write it. This results in smaller, more modular code; but, takes more time to complete.
The end of my Sentivate day is focused on catching up with advisors and reading status reports from core. I have an amazing team but we are looking for new developers and designers so if you’re interested please email me email@example.com or contact me directly on Discord.
Where are Sentivate’s current team members based out of? How do they usually collaborate with each other?
The core team is out of NJ, FL, and PA. We make use of various tools from iCloud, Mega, Dropbox, Slack, Discord, Telegram, Signal, Wunderlist, Evernote, Github, and Gitlab.
Tell us about how the idea for Sentivate originated.
Originally we were designing Sentivate to be a solution for private government intranets, or private Webs. After going through the many faults of the web and finding that many vulnerabilities were inherent, we slowly started to change direction. Eventually we realized the scope of what we were building and what was actually being created. As we continued to research solutions for things like built-in congestion control for packets cryptocurrency started to move into the mix. Decentralized aspects were initially part of the original design as it improved availability of static assets and increased scalability in addition to the centralized services.
In the current cryptocurrency ecosystem we see many projects trying to take on the issues of a centralized web, but don’t truly understand the drawbacks of a decentralized web, how does Sentivate stand out from the rest of the pack when it comes to this issue?
This is the most important question and it separates us from every single project in this space looking to replace the web as we know it. Such projects don’t realize how the web works and it’s true pain points and advantages. Two of those core issues are how the domain system functions on a technological level and the data transport protocol being HTTP. The Web’s core topology isn’t a pain point in fact it’s one of its greatest advantages.
We need a fast and cheap web. The next Web has to be faster and we need to reduce friction between client and service.
Introducing a cat protocol which further complicates logic will only slow down the web. Forcing a service or the Web to rely on blockchain technology will severely slow down the service in question and the entirety of the Web. Web 3.0 projects see blockchain as a magic bullet or a cash grab not a specific tool for very specific jobs. We see many large companies offering blockchain services for building blockchain products. Those who profited a ton during the rush were the companies selling the shovels. There is a reason why blockchain isn’t replacing all of our favorite centralized services. The answer is simple: blockchain, when not utilized appropriately and for the right purpose, bottlenecks the service and makes scaling a lot more difficult and costly. When Web 3.0 projects say “it happens all on-chain,” that’s called a pipe dream.
It becomes more and more evident that they can’t deliver what they promise when they need to create another network that tries to centralize the blockchain’s operations. They realize that it’s a terrible idea to go fully decentralized for our web, it’s simply not possible, and far from rational to do so. It’s also just another cash grab to incentivize investments rather than involvement and creating worthwhile technology. Funny it is that they would need to create an additional network to sell another token to deliver what they said they were going to deliver initially. Once they start admitting to the fact that portions of their blockchain must be centralized, it hints at a much larger technological flaw that gets down to physics. If data needs to traverse more space and time to get to be displayed on a service it’s going to be a lot slower than the web we have today. We can only move data so fast if it needs to move through additional logic in a consensus algorithm to even be considered you just introduced a bottleneck and an attack vector which could render the entire web running on it useless.
Web 3.0 projects don’t address the real issues they may say they are but are far from doing so. When they say they are fixing DNS but aren’t actually providing a solution simply selling a “.ETH” “domains” on the Ethereum network. They tend to complain about the regulatory body that is ICANN, but stay quiet about the actual issues that are broken with DNS. The best paper to read in regards to exploring the broken bits of DNS is MinimaLT. That’s a brilliant piece of work although they had limited vision and an incomplete implementation none the less still genius work. DNS needs to be encrypted by default and instead of just providing traditional DNS info instead it provides a full, signed cryptographic certificate. This provides essential future requirements like geo-location based routing and 0-RTT by default. Things as simple as emoticon based domain registrations should also be provided. The issues related to ICANN they tend to bring up is that it’s a centralized entity that could be bought by the person with the largest pockets and censor sites. The reality is that some sites need to be censored, and some owners stripped of their domains. Those running criminal organizations that profit off of their domain shouldn’t be allowed to, for example, subject children to harm and turn a profit. Terrorists shouldn’t have an outlet for funding. There is a fine line in the sand. On the other hand those with political affiliations shouldn’t be de-platformed or de-banked because of opposing political beliefs. Trademark and copyright law need to be observed as well; but not without due process to protect against predatory trademark practices by those big and small, alike. In response to things like underage pornography, Web 3.0 projects say they’ll maintain a blacklist meanwhile they said in the beginning and the whole reason for them being decentralized is to stop censorship. If we have a web that can’t have data removed and deleted we have a very serious ethical dilemma and technological issue. Web 3.0 projects get caught in a conniption and fail to use rationality when attempting to solve the current problems facing the Web.
Fat protocols are what Web 3.0 projects need to avoid and not falsely market as a protocol analogous to HTTP. Many fat protocols rely on HTTP which is exactly a part of the Web’s core issues. That’s why we are creating protocols that are leaner and are Data Transport Protocols, not application layer fat protocols that create additional walls between client and service.
Another core issue being ignored is that our solutions drastically reduce is the bandwidth crisis. Humanity is quickly outpacing our networks capabilities. New devices, people, and developing countries are coming online. The toaster, microwave, and the fridge now talk to Google/Apple/Alexa. The objects around us are becoming connected to the web and that puts a ton of strain on our networks. Our real-time demands put time constrained actions on all our applications, which means that our networks are going to be clogged up with constant and nearly instant updates.
The laws of physics can only move data so fast. We must focus on what would have the largest impact before data prioritization and speed lanes are our only option.
They focus on blockchaining and/or decentralizing everything under the sun while failing to address the most pressing issues with the correct technology. This leads me to believe they are either ignorant or looking to turn a quick buck and I don’t know which is worse. Considering many of these projects were funded millions and somehow fail to deliver a product, what they promised, or simply blew through all the capital makes me think a combination of both. It’s true that running a business depends on profit; but it also comes with the responsibility and a duty to do the right thing.
Can you explain what hApps are to people new to this concept? What makes Hybrid Apps different from dApps and how can they improve on the concept?
Hybrid Apps are designed to be better than traditional web apps & todays dApps. Hybrid apps are built around the idea of a constant stream of real-time data & only pushing data to the client that it needs at that exact moment. hApps build themselves as they are being used. In the background assets and dynamic data are streamed to the client which builds the GUI as you use it. If you were to slow down an hApp to a crawl you would see the app building itself section by section streaming in all the required assets.
Since assets rely on hash ids they can easily integrate into a P2PCDN. This is one aspect of how Hybrid apps take on their “hybrid” attributes. One thing we are working on is a network wide P2PCDN which allows users to gain Viat by distributing assets and contributing to the network. Assets which are present on multiple sites such as popular front-end libraries like: Ractive, React, Angular, jQuery, Vue, Acidjs, Backbone, and Underscore can be distributed efficiently distributed to clients. This further increases availability and scalability of the Universal Web.
Hybrid apps are reactive applications from the start. Our browser will continue to include a custom front-end framework built on our utility libraries and a reactive component library called Ractive which was originally developed at the Guardian.
Hybrid apps have improved real-time functionality over traditional web apps. Compared to traditional web apps hApps have UDSP which replaces both HTTP and WebSockets in functionality and purpose. The stream itself has more flexibility when reliability comes into play. UDSP is a bi-directional real-time stream which can push updates to clients or server the moment they happen. The same exact connection is used to also transfer over real-time assets.
Unlike dApps, hApps can provide improved GUI functionality and features over traditional web apps due to it being a faster and lighter real-time connection between server and client.
Tell us more about Sentivate’s domain name system, and what would be possible with it? Domain Abuse has practiced for years, what is Sentivate doing to solve that issue?
The Domain system is designed to categorize the web, limit abuse, limit predatory domain practices, add default 0-RTT capabilities, and improve security.
The Domain Information System is encrypted by default and provides the basis for 0-RTT to all end domain services. The DIS returns a certificate which includes routing information with cryptographic parameters to establishing an encrypted UDSP connection.
All domains must match their extension. A store like Newegg must operate on the .store extension. This categorization of domains are strictly enforced by domain rules and regulations.
The DIS can also take on decentralized aspects to improve availability, reliability, and evade censorship to a degree.
With all the things that Sentivate is going after, what do you think is the biggest problem Sentivate will solve and why is the problem important to solve?
When attempting to solve the bandwidth related concerns all the other issues we address need to be solved in the process. By solving the bandwidth problem we end up needing a better way to build apps, more efficient protocols, and a re-imagining of DNS just to start.
Can you give your opinion as to why a solution to this problem can only be covered by Sentivate? Why were there no projects before that addressed the realities of this problem?
Right now there is an ideology that is plaguing every other project. It’s that everything must either be decentralized or blockchain based. Decentralization and blockchain technologies have specific use cases but there must be a balance. The issues that we face are far more technical than just swapping to the opposite topology or introducing a different type of database. The issues we are solving and the unique technology we are proposing, (DIS & UDSP), not a single crypto project is actually proposing or even working on.
Do you feel Identity Certificates will eventually replace usernames and passwords? What are the benefits of having a single sign-on for the internet, and will this protect the privacy of users?
Yes, it’s the only logical progression for the Web. We are already starting to see things akin to this like OAuth. Because we are removing the human element and relying on strong cryptographic primitives, users’ privacy and security drastically increase. Attack vectors will shrink and the attack costs will drastically increase.
Relying on cryptographic keypairs for not only your online identity but for logging in, registering, and interacting with services is the future of web security.
What industries can you see applying the technology behind Sentivate and has there been any case studies?
Any industry that relies on the web today could take advantage of Sentivate. It has use cases for consumers, businesses, and governments. We see an immediate use case for disbursed computing, bandwidth constrained environments, banking, and real-time trading applications that want the fastest transactions possible.
What are some of the use cases of the SNTVT token and benefits of holding it currently?
SNTVT is an ERC20 utility token on the Ethereum network. Sentivate tokens are used to gain access to the early stages of the Sentivate Network, development process, & voting. Delegates, cast their votes during various phases of development which aids in directing the project. Delegates have early access to browsers, server modules, client modules, Identity certificates, Domain certificates, and various other applications. Delegates with more SNTVT tokens have more voting power and as such have a greater ability to steer the project. Delegates are SNTVT holders which can verify they own SNTVT in a wallet(s) via a signed message.
Tell us more about the Viat token and the importance it will have to the Sentivate network, is there any timeframe when will it be implemented?
Viat is the native cryptocurrency on the Sentivate Network. Viat has a hybrid blockchain. Viat’s core systems are decentralized focused but enhanced by decentralized components; the opposite of Sentivate’s Web. Viat is designed to be fast, secure, and have some of the lowest transaction fees available. Viat’s centralized portions can process instant transactions, provide wallet security, and alleviate network congestion when the decentralized network is under heavy load. However, these centralized features are opt-in only allowing users to forge their own path.
Viat has a dynamic proof of work which can be mined two ways. Direct mining is the main method & the second method is through the use of packet puzzles in UDSP. Packet puzzles allow for passive mining of Viat while browsing the Universal Web. However, it’s not enabled by default. The situations which arise that enable packet puzzles are: upon connection handshake, connection liveliness check, DDoS protection, congestion control, and or the service chooses to enable it for their own reasons. It is up to the service to enable packet puzzles. This ensures that there is no need for constant mining in the background and gives real purpose to the mining process. Otherwise, it would be on all the time sucking up resources & eating into battery life.
Identity & Domain certificates also double as Viat wallet keys. This allows users to not only instantly sign into a service during connection handshake but also provide a way to purchase goods from services, tip sites, and or refund clients.
Viat is an integral part of the full functionality of the Universal Web, without it only part of the picture is there.
Being in cryptocurrency space, we have seen extraordinary growth in the past two years, what have you experienced and learned in that time that will inform you and the Sentivate team for 2019 and the years ahead?
Understanding the market and it’s cycles are fundamental to being in crypto. Using the insight we gained in the sphere I’ve come to the conclusion that consistently doing the right thing gradually bends the fabric of the multiverse to your highest ideal and will. So basically do the right thing always.
Can you give us any details on any new partnerships with Sentivate?
We tend to keep quiet about any higher level operations or initiatives. When we are ready to announce, becomes ethical to, and legal to do so we will. None the less we are focused on specific strategic partnerships in particular.
What are your thoughts on the crypto market, short term and long term?
I think the regulation that is coming is exactly what the scene needs to establish legitimacy in the eyes of retail consumers, businesses, and investors. The Crypto Wild West cannot last forever. I see this as a bullish sign for legitimate cryptocurrency projects around the world. As the legacy financial and web decay it will only spur innovation and growth to replace the old systems with new systems.
Where do you and Sentivate see the world of blockchain being in years to come?
I expect the vast majority of projects to completely fail to deliver what they have promised. The few that end up delivering will end up creating markets out of everything which will be a huge win for the consumer by driving down costs and optimizing efficiency. The projects providing infrastructure and utilities to build applications and solve problems will survive. Any project not offering unique technology will survive and be a part of the development of the new web.
Thanks again for all of your answers Tom and for taking the time to do this interview. If people want to follow Sentivate and stay up to date with what’s going on, where should they go?