-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Yeah, but in swarm initialization we're overloading these maps to
indicate liveliness, where as StorageMapping indicates membership in
the defined by parent sense. And there will be situations where you
want to detect if a host has not sent a heartbeat and should be booted
out of the swarm. There could just be a function for detecting this
though, the maps definitely aren't required.



On 02/17/2014 12:22 AM, DavidVorick wrote:
> In src/swarm/block.go:
> 
>> 
>> -	EntropyStage1 map[string][]byte -	EntropyStage2
>> map[string][]byte +	EntropyStage1 map[string]string +
>> EntropyStage2 map[string]string
> 
> The way I was thinking that it was going to work:
> 
> 1. receive block (set of heartbeats + set of ack maps) 2. order
> heartbeats (according to spec, using entropy from the previous 
> block) 3. process heartbeats 1-by-1, putting stage 2 stuff into a 
> function-specific map (IE a map defined within the processing 
> function, and not appearing in any structs) 4. verify storage
> proofs and create entropy seed out of the function-specific maps
> 
> so you never actually pull all of the data out into a struct, and
> most of the data doesn't get pulled out at all. It's processed once
> and then discarded. (hashes of updates are saved so that we know
> which have been processed before)
> 
> — Reply to this email directly or view it on GitHub 
> <https://github.com/Siacoin/Sia/pull/12/files#r9782501>.
> 

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.22 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iQEcBAEBAgAGBQJTAZ0yAAoJEHP1nN3uZoHub/oH/1J0YB4YxpNRiDjtyhU4h4eq
5VtloOv3nuX1AN1WlHDo7QeCl1230AA+MG3RAH9vYoM+1piwn0K+akDm8pbZsocF
5MofbJ3O7TUo/IHEw9jcUuIntvbiufKtQEpHpWADbkplPvZ2EsUHuqjTW0AIzF1m
tGGqeT0bJ/Z6yySW0RLCpKAGdb/vdDmWk2Kvx8V5V/MLd8jmga4A63F27+IcVV0l
TCqXR80h08cpmsxCMR8JuKGWHNWQpYF0IVf4mUzg0rIfVgYozWjVfaBeLBEaHgKg
16R6kROUj0GqIrW8e7+bFMRefIZu1lWPZzNRClEpJXjPW1zGM57Rrs4Ney/fqWc=
=yStH
-----END PGP SIGNATURE-----