mirror of
https://github.com/Decentralized-ID/decentralized-id.github.io.git
synced 2024-12-14 18:14:27 -05:00
65 lines
5.5 KiB
Markdown
65 lines
5.5 KiB
Markdown
* [Announcing Pico Engine 1.0](https://www.windley.com/archives/2021/02/announcing_pico_engine_10.shtml)
|
||
> In addition to the work on the engine itself, one of the primary workstreams at present is to complete Bruce Conrad's excellent work to use DIDs and DIDComm as the basis for inter-pico communication, called ACA-Pico (Aries Cloud Agent - Pico). [...] This work is important because it will replace the current subscriptions method of connecting heterarchies of picos with DIDComm. [...] because DIDComm is protocological, this will support protocol-based interactions between picos, including credential exchange.
|
||
|
||
* [ACA-Pico working group](https://docs.google.com/document/d/12dWUFyL7u6OQkhnPObJOOlV-U2LDoHpF-ZQLj3hXbjA/edit)
|
||
|
||
* [Picolab/aries-cloudagent-pico](https://github.com/Picolab/aries-cloudagent-pico)
|
||
* [Announcing Pico Engine 1.0](https://www.windley.com/archives/2021/02/announcing_pico_engine_10.shtml)
|
||
> In addition to the work on the engine itself, one of the primary workstreams at present is to complete Bruce Conrad's excellent work to use DIDs and DIDComm as the basis for inter-pico communication, called ACA-Pico (Aries Cloud Agent - Pico). [...] This work is important because it will replace the current subscriptions method of connecting heterarchies of picos with DIDComm. [...] because DIDComm is protocological, this will support protocol-based interactions between picos, including credential exchange.
|
||
* [Introduction to Picos](https://iiw.idcommons.net/4C/_Introduction_to_Picos) by Phil Windley
|
||
|
||
IoT, digital twins, device shadows, Conflict-free replicated data type (CRDT), CSP over DIDcomm
|
||
|
||
* [https://picolabs.io](https://picolabs.io) Pico Labs
|
||
|
||
* [https://github.com/Picolab/](https://github.com/Picolab/) repos
|
||
|
||
* [https://picolabs.atlassian.net/wiki](https://picolabs.atlassian.net/wiki) documentation
|
||
|
||
* [http://stackoverflow.com/questions/tagged/krl](http://stackoverflow.com/questions/tagged/krl) programming Q&A
|
||
|
||
* [Announcing Pico Engine 1.0](https://www.windley.com/archives/2021/02/announcing_pico_engine_10.shtml)
|
||
|
||
Pico is short for “Persistent Compute Objects.”
|
||
|
||
Why Picos
|
||
|
||
- Persistent, personal, computational nodes → More individual autonomy
|
||
- Computational node for anything: person, place, organization, smart thing, dumb thing, concept, even a pothole
|
||
- Better, more scalable model for IoT → trillion node networks
|
||
- Picos support social things and trustworthy spaces
|
||
- Better sharing, more natural relationship-based interactions (borrow my truck, Fuse with two owners)
|
||
- Scales
|
||
- Substitutable hosting model → freedom of choice
|
||
- pico mesh
|
||
|
||
* [...]
|
||
|
||
What are Picos?
|
||
|
||
- “Pico” is a neologism for persistent compute objects.
|
||
- Persistence is a core feature of how picos work.
|
||
- Picos exhibit persistence in three ways:
|
||
- Persistent identity—Picos exist, with a single identity, continuously from the moment of their creation until they are destroyed.
|
||
- Persistent state—Picos have state that programs running in the pico can see and alter.
|
||
- Persistent availability—Picos are always on and ready to process queries and events.
|
||
|
||
Pico Engine 1.0 released in January
|
||
* [Persistence, Programming, and Picos](https://www.windley.com/archives/2021/02/persistence_programming_and_picos.shtml) -
|
||
> Picos show that image-based development can be done in a manner consistent with the best practices we use today without losing the important benefits it brings.
|
||
|
||
> The project name, PICOS, is an abbreviation of “Privacy and Identity Management for Community Services”. The objective of the project is to advance the state of the art in technologies that provide privacy-enhanced identity and trust management features within complex community-supporting services that are built on Next Generation Networks and delivered by multiple communication service providers. The approach taken by the project is to research, develop, build trial and evaluate an open, privacy-respecting, trust-enabling identity management platform that supports the provision of community services by mobile communication service providers.
|
||
>
|
||
> Learn more about the [motivation](http://www.picos-project.eu/Motivation.181.0.html), the [objectives](http://www.picos-project.eu/Objectives.182.0.html), [tasks](http://www.picos-project.eu/Tasks.183.0.html) and [achievements](http://www.picos-project.eu/Achievements.190.0.html) of PICOS, and get to know the PICOS exemplary [communities](http://www.picos-project.eu/Communities.184.0.html).
|
||
* [Announcing Pico Engine 1.0](https://www.windley.com/archives/2021/02/announcing_pico_engine_10.shtml) Windley
|
||
|
||
I'm excited to announce a new, stable, production-ready pico engine. The latest release of the Pico Engine (1.X) provides a more modular design that better supports future enhancements and allows picos to be less dependent on a specific engine for operation.
|
||
|
||
* [Building Decentralized Applications with Pico Networks](https://www.windley.com/archives/2021/02/building_decentralized_applications_with_pico_networks.shtml)
|
||
|
||
|
||
* [Ten Reasons to Use Picos for Your Next Decentralized Programming Project](https://www.windley.com/archives/2021/07/ten_reasons_to_use_picos_for_your_next_decentralized_programming_project.shtml)
|
||
|
||
Summary: Picos are a programming model for building decentralized applications that provide significant benefits in the form of abstractions that reduce programmer effort. Here are ten eleven reasons you should use picos for your next decentralized application. Temperature Sensor Network Built from Picos I didn't start out to write a programming language that naturally supports
|
||
|