--- Day changed Wed Jul 24 2019
10:52 -!- calvin [~calvin@110.14.152.121] has joined #utreexo     
10:52 -!- calvin is now known as Guest93600     
10:53 -!- Guest93600 [~calvin@110.14.152.121] has quit [Client Quit]     
10:55 -!- kcalvinalvin [~calvin@110.14.152.121] has joined #utreexo     
10:57 < kcalvinalvin> I must be missing something but is there a need for Pollard?
11:02 -!- kcalvinalvin [~calvin@110.14.152.121] has quit [Remote host closed the connection]     
11:03 -!- kcalvinalvin [~calvin@110.14.152.121] has joined #utreexo     
12:06 -!- kcalvinalvin [~calvin@110.14.152.121] has quit [Remote host closed the connection]     
12:06 -!- kcalvinalvin [~calvin@110.14.152.121] has joined #utreexo     
13:55 -!- kcalvinalvin [~calvin@110.14.152.121] has quit [Remote host closed the connection]     
21:09 -!- kcalvinalvin [~calvin@110.14.152.121] has joined #utreexo     
21:14 -!- kcalvinalvin [~calvin@110.14.152.121] has quit [Ping timeout: 268 seconds]     
22:14 -!- kcalvinalvin [~calvin@118.131.103.244] has joined #utreexo     
23:18 < adiabat> kcalvinalvin: yes it's needed; the forest struct can only hold the whole forest, while pollard can have only some nodes populated
23:19 < adiabat> having both forest and pollard is somewhat redundant because the both re-implement the same thing
23:19 < adiabat> but maybe it's forest that could be removed
23:21 -!- kallewoof [~quassel@240d:1a:759:6000:a7b1:451a:8874:e1ac] has joined #utreexo     
23:22 < adiabat> because you could have a pollard where everything is populated and that would probably still work OK
23:23 < adiabat> but maybe that would be less efficient because of all the pointers, which forest doesn't need as it saves everything all in order