HackMD
    • Create new note
    • Create a note from template
    • Sharing Link copied
    • /edit
    • View mode
      • Edit mode
      • View mode
      • Book mode
      • Slide mode
      Edit mode View mode Book mode Slide mode
    • Customize slides
    • Note Permission
    • Read
      • Only me
      • Signed-in users
      • Everyone
      Only me Signed-in users Everyone
    • Write
      • Only me
      • Signed-in users
      • Everyone
      Only me Signed-in users Everyone
    • Commenting & Invitee
    • Publishing
      Please check the box to agree to the Community Guidelines.
      Everyone on the web can find and read all notes of this public team.
      After the note is published, everyone on the web can find and read this note.
      See all published notes on profile page.
    • Commenting Enable
      Disabled Forbidden Owners Signed-in users Everyone
    • Permission
      • Forbidden
      • Owners
      • Signed-in users
      • Everyone
    • Invitee
    • No invitee
    • Options
    • Versions and GitHub Sync
    • Transfer ownership
    • Delete this note
    • Note settings
    • Template
    • Save as template
    • Insert from template
    • Export
    • Dropbox
    • Google Drive Export to Google Drive
    • Gist
    • Import
    • Dropbox
    • Google Drive Import from Google Drive
    • Gist
    • Clipboard
    • Download
    • Markdown
    • HTML
    • Raw HTML
Menu Note settings Sharing Create Help
Create Create new note Create a note from template
Menu
Options
Versions and GitHub Sync Transfer ownership Delete this note
Export
Dropbox Google Drive Export to Google Drive Gist
Import
Dropbox Google Drive Import from Google Drive Gist Clipboard
Download
Markdown HTML Raw HTML
Back
Sharing
Sharing Link copied
/edit
View mode
  • Edit mode
  • View mode
  • Book mode
  • Slide mode
Edit mode View mode Book mode Slide mode
Customize slides
Note Permission
Read
Only me
  • Only me
  • Signed-in users
  • Everyone
Only me Signed-in users Everyone
Write
Only me
  • Only me
  • Signed-in users
  • Everyone
Only me Signed-in users Everyone
Comment & Invitee
Publishing
Please check the box to agree to the Community Guidelines.
Everyone on the web can find and read all notes of this public team.
After the note is published, everyone on the web can find and read this note.
See all published notes on profile page.
More (Comment, Invitee)
Commenting Enable
Disabled Forbidden Owners Signed-in users Everyone
Permission
Owners
  • Forbidden
  • Owners
  • Signed-in users
  • Everyone
Invitee
No invitee
   owned this note    owned this note      
Published Linked with GitHub
Like BookmarkBookmarked
Subscribed
  • Any changes
    Be notified of any changes
  • Mention me
    Be notified of mention me
  • Unsubscribe
Subscribe
# Holochain commons An open ideas document and a wish list for common functionality the dev community needs and possibly would like to develop. [Zome traits](#Zome-traits) [Design patterns](#Design-patterns) [Standalone DNA / hAPP](#Standalone-DNA--hApp) [Potential core functionality](#Potential-core-functionality) # Zome traits Standardised traits would allow for third party apps to better access and visualise an agents data (DNA-instances/zomes/entries) but also to interact with the data in a meaningful way. It faciltates better interopability between apps and speeds up development. ### `Implements` List which standard traits (and possibly trait versions) a zome uses. Possibly the trait definitions in the zome code are sufficient? But I have a sense we would like to have one more level of detail - trait id, a version number etc. The information has to be accessible not only for the app developer but for third party apps calling zome functions. (Similar to `IERC165`, `supportsInterface(interfaceId)` https://docs.openzeppelin.com/contracts/2.x/api/introspection) ### [`Ownable`](https://hackmd.io/kWfnGNR4Ta-K1h0jpK71Hw?both) The notion of “ownership” over a digital resource is a basic pattern many Holochain applications will need. With ownership comes the user expectance of being able to transfer that ownership, to renounce ownership, etc. https://hackmd.io/kWfnGNR4Ta-K1h0jpK71Hw?both ### `Metadata` Both zome level fields and entry level fields. Standard (`zome_description`, ...) as well as zome/app specific. ### `Taxonomy` Provides a list of categories for other things. ### `Preview` Renders a human readable preview of an entry or list of entries, possibly returns a [webcomponent](https://www.webcomponents.org/)? Example: embed a nice looking representation of a chat entry in a humm blog post. ### `Editor`? or `Plugin`? Returns a plugin editor that can be embedded in other apps. Example: Every Humm blog post embeds a "Comments Editor" from the "HoloComments" app allowing for users to comment posts. ### `Timestamped` Entries carry metadata that give varying levels of proof that they happened at a certain moment in time. (cf [Mixin zome(s) for entry timestamping](https://forum.holochain.org/t/mixin-zome-s-for-entry-timestamping/1307/)) ### `ClaimsPermissioned` Actions are allowed or denied based on the possession of valid claims/credential (cf W3C Verifiable Credentials). ### `MembersOnly` A special application of ClaimsPermissioned that requires a valid credential to join the network. ### `DIDResolver` Able to take responsibility for resolving [W3C Decentralised Identifiers](https://www.w3.org/TR/did-core/) for the data this DNA’s DHT contains. (cf [Mixin zome and utility libraries for RESTful APIs and URI resolvers](https://forum.holochain.org/t/mixin-zome-and-utility-libraries-for-restful-apis-and-uri-resolvers/2071)) ### `Signable` Signing: something that allows arbitrary participants to sign other entries by hash, thus indicating that they have seen and agreed with the information contained therein. # Design patterns ### `BlobStorage` Supports the storage and retrieval of chunked blobs and their manifests. **This could as well be a standalone DNA other DNAs can interact with.** ### `Indexing patterns` ...for browsing and retrieving other entries. I’ve seen [anchors](https://github.com/holochain/anchors) and [DAGs](https://github.com/holochain/basic-chat/pull/6) (both have their use-cases), there are probably other flavours needed too. # Standalone DNA / hApp ### `Annotation` Able to annotate other data, either in the same zome/DNA, in some other DNA, or outside of Holochain entirely. Should probably be polymorphic, e.g., `Annotation<BlogPost>`. ### `Presence` Shows whether an agent is online, offline, available, busy, typing, idle, etc. ### `Scheduling` Shows whether an agent is available or occupied at a given date in the future. ### `Events` Calendars, etc. Can be composed with Scheduling to do some cool things. ### `Messaging` Chat, IM, DM, comments, etc. ### `Posting` Similar to Messaging but meant for syndication. May just be an application of Messaging. ### `Notification` Allows agents to subscribe to things they want to be notified on; emits notification signals to clients. ### `Notary` Able to witness, and guarantee the uniqueness of, events. ### `LinkRegistry` Zome that tracks links incoming / outgoing between the host DNA and other DNAs using [XDI Link Contract](https://en.wikipedia.org/wiki/Link_contract) schema. We would also want this as a standalone DNA that tracks links between two other DNAs. ### `Presence` Shows whether an agent is online, offline, available, busy, typing, idle, etc. ### `Identity` Able to make assertions about facets of an agent’s identity, whether in a legally recognised (e.g., driver licensing office) or an informal capacity (web of trust). # Potential core functionality ### `GroupAgency` Agents can form recognisable groups with persistent identifiers; group membership (= authority to act as group representative) can be verified by third parties. Related to ClaimsPermissioned. (ping @pospi, cf [How will Holochain handle group agents?](https://forum.holochain.org/t/how-will-holochain-handle-group-agents/1095) ) ### `MultiNodeAgent` This DNA is capable of combining multiple agent public keys into one human representation. Similar to GroupAgency and may be able to take advantage of the same codebase. ### `ExistenceCheck` Simple API that checks if entries with given hashes exist in the DNA, for use by other DNAs that need to perform referential integrity checks. ### `Timestamping` Able to provide a timestamp for external entries, at varying levels of proof. Naturally, this can support `Timestamped`. ### `Persistent Off-Chain Storage` Provide a way to cache expensive computations and data-structures without poluting the source chain with transient data.

Import from clipboard

Advanced permission required

Your current role can only read. Ask the system administrator to acquire write and comment permission.

This team is disabled

Sorry, this team is disabled. You can't edit this note.

This note is locked

Sorry, only owner can edit this note.

Reach the limit

Sorry, you've reached the max length this note can be.
Please reduce the content or divide it to more notes, thank you!

Import from Gist

Import from Snippet

or

Export to Snippet

Are you sure?

Do you really want to delete this note?
All users will lost their connection.

Create a note from template

Create a note from template

Oops...
This template is not available.


Upgrade

All
  • All
  • Team
No template found.

Create custom template


Upgrade

Delete template

Do you really want to delete this template?

This page need refresh

You have an incompatible client version.
Refresh to update.
New version available!
See releases notes here
Refresh to enjoy new features.
Your user state has changed.
Refresh to load new user state.

Sign in

Forgot password

or

By clicking below, you agree to our terms of service.

Sign in via Facebook Sign in via Twitter Sign in via GitHub Sign in via Dropbox

New to HackMD? Sign up

Help

  • English
  • 中文
  • Français
  • Deutsch
  • 日本語
  • Español
  • Català
  • Ελληνικά
  • Português
  • italiano
  • Türkçe
  • Русский
  • Nederlands
  • hrvatski jezik
  • język polski
  • Українська
  • हिन्दी
  • svenska
  • Esperanto
  • dansk

Documents

Tutorials

Book Mode Tutorial

Slide Mode Tutorial

YAML Metadata

Contacts

Facebook

Twitter

Discord

Feedback

Send us email

Resources

Releases

Pricing

Blog

Policy

Terms

Privacy

Cheatsheet

Syntax Example Reference
# Header Header 基本排版
- Unordered List
  • Unordered List
1. Ordered List
  1. Ordered List
- [ ] Todo List
  • Todo List
> Blockquote
Blockquote
**Bold font** Bold font
*Italics font* Italics font
~~Strikethrough~~ Strikethrough
19^th^ 19th
H~2~O H2O
++Inserted text++ Inserted text
==Marked text== Marked text
[link text](https:// "title") Link
![image alt](https:// "title") Image
`Code` Code 在筆記中貼入程式碼
```javascript
var i = 0;
```
var i = 0;
:smile: :smile: Emoji list
{%youtube youtube_id %} Externals
$L^aT_eX$ LaTeX
:::info
This is a alert area.
:::

This is a alert area.

Versions

Versions and GitHub Sync

Sign in to link this note to GitHub Learn more
This note is not linked with GitHub Learn more
 
Add badge Pull Push GitHub Link Settings
Upgrade now

Version named by    

More Less
  • Edit
  • Delete

Note content is identical to the latest version.
Compare with
    Choose a version
    No search result
    Version not found

Feedback

Submission failed, please try again

Thanks for your support.

On a scale of 0-10, how likely is it that you would recommend HackMD to your friends, family or business associates?

Please give us some advice and help us improve HackMD.

 

Thanks for your feedback

Remove version name

Do you want to remove this version name and description?

Transfer ownership

Transfer to
    Warning: is a public team. If you transfer note to this team, everyone on the web can find and read this note.

      Link with GitHub

      Please authorize HackMD on GitHub

      Please sign in to GitHub and install the HackMD app on your GitHub repo. Learn more

       Sign in to GitHub

      HackMD links with GitHub through a GitHub App. You can choose which repo to install our App.

      Push the note to GitHub Push to GitHub Pull a file from GitHub

        Authorize again
       

      Choose which file to push to

      Select repo
      Refresh Authorize more repos
      Select branch
      Select file
      Select branch
      Choose version(s) to push
      • Save a new version and push
      • Choose from existing versions
      Available push count

      Upgrade

      Pull from GitHub

       
      File from GitHub
      File from HackMD

      GitHub Link Settings

      File linked

      Linked by
      File path
      Last synced branch
      Available push count

      Upgrade

      Danger Zone

      Unlink
      You will no longer receive notification when GitHub file changes after unlink.

      Syncing

      Push failed

      Push successfully