Message:

          Time:

  Reference:

         Dime:

TSN Address:

TSN Signature:

bc1qu0tknvdyatprq68mkee0g7zgtnthe5vtr8lyyd

H80zEeADBZbH4XS52H1tlSBSXjfBt3dzQhh0D6mjFSybJMPOeQoxloKZWkIFn2u3/CZ3Rup2dX9eTV9cUjyQ01A=

2020-09-09 15:09 647486,2690 1909824,66
H9pjb3Yzrg6RNCpGD8BmFZUCO6/rqAHFuxQSBuLZn+FZVvdhSU2WegDH+S4L6sID+2hl9iL9uglaQG64Xexvb/g=
Patriot, i'm ns u understand the significance of this! Using 'thread channels' not only
have u created dime replies, but u have effectively created a mechanism for a comments section
IN ANY directory. Further, using a similar mechanism but with 1/3 signing (only sigs) two TSN addresses
could create DMs by simply exchanging the proofs (but not publishing)...brilliant. So, would individual
'thread channel' sigs have their own unique TSN Signature Pages?

1

1

2

2020-09-10 13:04 647607,1801 1910337,22
H80zEeADBZbH4XS52H1tlSBSXjfBt3dzQhh0D6mjFSybJMPOeQoxloKZWkIFn2u3/CZ3Rup2dX9eTV9cUjyQ01A=
Here's how this works...the Thread Channel opener always has the ability to publish the current
state if they so please. Until they are ready to do so there's no need for any TSN Signature pages.
The original Dime issuer (should they choose to reply) responds on the original Dime Sig Page.
The back and forth can go on as long as need be. Using 2/3 signing the channel state is
continually updated by both parties (or more for 'branches' LOL). If and when the channel
thread opener ever decides to publish--the thread page moves to the Dimes directory w/ appropriate
Sig Page URL, and 3/3 signing officially creating a TSN Reference using the most recent sig.
While it technically is only 1 TSN Reference...all prior state proofs r built into the final sig
and remain on the sig page. Make sense? Let's try it. BTW I raise u one--just pinged u what
i'm calling 'functional ping proofs' (In this case Like and ReDime sigs)...now u can Like/ReDime
anyone's Dime by Pinging them these proofs. Only the recipient need publish the proof/link to them in tally.

          Time:

         Reply:

         Dime:

bc1qpjac5k7dcpchz7y23nj3gl942qtsxy90eh9wkm

blah

asdf

asdf

adsf