search results

25 ( ) from offset 0 out of 85

539 description Byzantine Askemos Language Layer
604 SystemRequirements description ## Essential 1. Any one of the supported compilers: * [Chicken Scheme][1] – as of Jun 2013 at least the latest development version. However that's untested. You might still need to
611 InstallFromSource description ## 1 Install Chicken Compiler Download and install from [][1] ## 2 Compile and Install the Binary Best: install current version. Follow instructions from [gitlab][2] . To install older
859 BALL Initial Expression Language description It should be stressed that any language worth it's salt would do. After all a contract can always establish it's own language. The initial language must at minimum allow to invoke processing of the co
839 CouchDB description <table> <tr> <td>Feature</td> <td>CouchDB</td> <td>BALL</td> </tr> <tr> <td>Protocol Format</td> <td>JSON</td> <td>XML</td> </tr> <tr> <td>Sync Method</td> <td>one way (both ways
889 description Bug Reports
896 description Things we'd like to have.
906 urn:about:/news description At the maintainers discretion.
947 download description ### Unreleased Source Code 2017-03-10: Moving to [a gitlab repo][1] in order to make things easier to update. Self-hosting on a byzantine fault tolerant network of small computers at home was cool. Am
969 FAQ description 1. Q: Do I have to have a dedicated hardware or can I run it at my desktop machine (or tablet, phone etc.)? A: No dedicated hardware required. In fact it's often installed at the users de
997 description Things to be changed for better.
1047 1 description A catch-all milestone for un-scheduled features.
1113 2 description Get rid of cruft.
1257 SACSP description (draft text) ## Intro The protocol is a *simplified byzantine paxos* Compare with [requirements][1] to highlight differences. Should this include references to other alternatives? The consensu
1312 3 description In light of year 2013 news, check that TLS code conforms to state of the art.
1341 documentation description ## Concepts And Internals * A birds eyes view on [request processing][1] * How [user code][2] is located and invoked. * A commented example of the [meta data][3] the BALL systems maintains for ea
3763 documentation description ## Usage * TBD Howto and first steps. 1. Semantics rest on unreliable, unidirectional message passing with *share nothing* semantics. This choice was inspired by and follows the mo
1345 ExampleMetadata description Ae740e7b8027e5be4abc3b1b951701b73
1455 ego description Ego: one of the user’s own pseudonyms. A user can have multiple pseudonyms, or alter egos.
1449 home (GNUnet) description Home: one of the user’s own places, hosted by one of the user’s egos.
1469 nym description Nym: a pseudonym (identified by their ECC cryptographic key) of another user in the system.
1463 OID description [See Askemos][1]. The *"unique self-sealing identifier"* (not the human readable name) of `` place ``. ### Hash Function #### Hashed Information The hash function must ensure that each object (place
1475 host (GNUnet) description Host: the pseudonym (identified by their cryptographic key) who is the owner of a place or home.
1893 become (BALL Core) description The content of this element becomes the next internal state (body) of the current place.
1895 link (BALL Core) description ## Purpose Register a new channel linking to either a given (id/ref) or a newly created (new) target. ## Syntax <link name="NAME">{id,ref,new}</link> <id>LITERAL OID</id> TBD: