Future releases of PolySwarm will be developed in accordance with changes in the threat market and actual network usage. Based on the observed usage of PolySwarm, we believe that the following features are all opportunities to benefit the network: resilient "artifact" confidentiality; basic: "artifact" selective publication to specific experts and SaaS service providers; Advanced: "Artifacts" are never exposed to anyone outside of the fully homomorphic engine's SGX enclaves; new tools (eg: subscribing to out-of-the-box threat feeds); deployment support for endpoint worker engine containers that can replace today's Endpoint Protection Suite.
The second stable release of PolySwarm has two main goals: (1) expand "bids" and "bounties" to handle a wider variety of "artifacts" (eg: URLs and web streams) (2) ease enterprise and PolySwarm usage by individual users. Future releases of PolySwarm should be able to handle a wider variety of "artifacts" such as automatic phishing detection by making "bounties" and "bids" directly to URLs and website content. Expanding protection for end users will be a priority for PolySwarm once stable development is complete. We look forward to developing an open source reference instance of an endpoint protection suite that automatically blocks malicious "artifacts" with PolySwarm intelligence, and we believe this public proxy framework is critical to widespread adoption.
Before moving from the PolySwarm test network (test token) to the real PolySwarm market, the focus of the PolySwarm 1.0 stable release is to clear bugs in the PolySwarm Gamma release. If time/funds allow, the larger goal of PolySwarm 1.0 stable version is to launch advanced "artifact" security technology, and only issue "rewards" to limited participants.
PolySwarm Gamma Edition will focus on delivering matchmaking capabilities to facilitate collaboration among “delegates”, “experts”, and “arbiters” who will be able to encapsulate expertise into “work engines” for specific types of “artifacts” . We expect that they will be able to advertise these "job engines" in the PolySwarm registration system, which should allow "delegates" to use "job engines" in a risk-free manner prior to the release of PolySwarm 1.0 (the Gamma version will continue using the PolySwarm testnet). Additionally, the Gamma release will consider enhancing and expanding the Bounty tool based on feedback and experience with Alpha and Beta releases. For example, we expect this to be beneficial to a "bounty" system: being able to solicit assertions from other "experts" (confidentiality), and only reveal them after the "assert" deadline. We expect the PolySwarm Gamma release to accomplish the following goals: a Worker Description Language (WDL) that describes artifact analysis capabilities and attribution of expert authorship (for reputation); a distributed, searchable work engine registry and its associated capabilities; Confidentiality of "Bounty Assertions" until deadline; completion of the selection of "Arbiter", response, and end-to-end "Bounty" feedback loop; we expect full marketplace functionality for the Gamma version.
The PolySwarm Beta will focus on delivering support for "PolySwarm Bids" via Raiden network channels. Compared to Bounties, Bids are designed to facilitate a higher volume of artifact evaluations, which also require more efficient settlement of each transaction on the blockchain. PolySwarm Beta will provide smart contracts, and we expect this functionality to be implemented as a direct, peer-to-peer Raiden channel between "delegates" and "experts" (using the testnet). We expect PolySwarm Beta to accomplish the following goals: Bid on channels; establish distributed "channels"; settle NCTs "when the channel is closed"; reference execution instances that generate and respond to "bids"; collect "fees" and dispatch smart contracts; Quantify the trust (in NCT) required to quantify the amount of a specific "artifact"; Bid/Bounty Development Kit: A test package and implementation framework for "experts" and "representatives" to automatically propose "bounties" and "bids".
After a successful token sale, the PolySwarm Alpha release will focus on delivering a prototype of the "Bounty" end-to-end workflow. This initial release will initiate an active development process by the PolySwarm team, and "representatives" and "experts" will be able to pass the PolySwarm test network ( "testnet") to trade. There will be basic "reward" smart contracts on the PolySwarm testnet, allowing "representatives" to issue "rewards", "experts" to make "assertions", and "representatives" to make "verdicts". We expect PolySwarm Alpha to accomplish the following goals: "Bounty Manager" smart contracts that save "bounty amounts" and "fees", accept "assertions", issue "verdicts", reward correct "experts"; for "artifacts" Non-PolySwarm storage (e.g. S3 and/or IPFS) published and withdrawn; prototype algorithm for selecting an "arbiter" at the end of the "bounty"; refer to the announcement "Bounty", response "assertion", and "arbiter" Decide on real facts, etc. Execution instance.
See More