| 8 Aug 2018 |
 komodobridge | [discord] <FishyGuts> But the contract has to have shielding, or thats gonna be a hard sell in my real estate world. | 05:14:00 |
| komodobridge | [discord] <FishyGuts> As a side note, every time I think of KMD I just get excited for the future of blockchain tech and this project in particular. Keep it up! 🎲 | 05:17:35 |
| komodobridge | [discord] <Mylo(KomodoPioneers)> @FishyGuts if you sent me KMD by transparent address, then i sent your customer KMD by z-addr, all that is known is that i sent to an amount to a z-addr. Replace "i sent" with "contract sends". Your customer still has privacy. | 05:26:17 |
| komodobridge | [discord] <FishyGuts> So how does the smart contract work in a case where say, a client signs up for automatic monthly payments? Is their information for their loan servicing contract kept private? | 05:41:30 |
| komodobridge | [discord] <jl777c> need a bit more details on exactly what the contract needs to do. You can send payments to a CC address and then restrict how it is able to be spent. from what you describe, what is missing is where the funds for the automatic monthly payments comes from. If it is all funded upfront, then it wouldnt be hard at all. the rule for payout would simply be, every month pay address X, a certain amount. And it would be setup so either your node or the receipient node can collect the monthly payment | 08:05:44 |
| komodobridge | [discord] <jl777c> the current examples are all variations on:
1. create a plan
2. add funds to the plan
3. payout funds the plan according to some specifiic set of rules | 08:06:32 |
| komodobridge | [discord] <jl777c> I guess we could define a payments CC, where anybody at anytime could create a plan and add funds to it as they have it. Separately, they would create/cancel? autopayments, which would authorize spending funds from the locked amounts | 08:07:58 |
| komodobridge | [discord] <jl777c> this would allow to collect earnings into a single address and not have to worry about sending payments out | 08:08:29 |
| 12 Dec 2018 |
|  noashh invited noashh2. | 21:46:43 |
| 14 Dec 2018 |
| noashh changed their display name from noashh-komodo to noashh-komodo (Old). | 13:06:47 |
| noashh changed their display name from noashh-komodo (Old) to noashh-komodo. | 13:15:54 |
| 19 Dec 2018 |
| noashh2 joined the room. | 22:15:05 |
| 23 Dec 2018 |
| noashh changed their display name from noashh-komodo to noashh-old. | 17:41:54 |
| noashh2 changed their display name from noashh-komodo to noashh. | 17:45:32 |
| noashh2 changed their display name from noashh to noashh2. | 22:25:58 |
| 26 Dec 2018 |
| noashh changed their display name from noashh-old to noashh1. | 19:47:32 |
| 17 Feb 2019 |
| noashh set a profile picture. | 14:43:00 |
| 27 Feb 2019 |
| noashh changed their display name from noashh1 to noashh. | 23:05:36 |
| 20 Apr 2019 |
| noashh changed their display name from noashh to noashh-now-on-rocketchat. | 10:51:43 |
| 26 Aug 2019 |
|  @ezsuitiotic6:matrix.org joined the room. | 03:53:50 |
| @ezsuitiotic6:matrix.org left the room. | 03:54:03 |
| 7 Jul 2020 |
|  @isis183:matrix.org joined the room. | 15:35:01 |
| 8 Jul 2020 |
| @isis183:matrix.org left the room. | 00:33:28 |
| 18 Apr 2022 |
|  @wybpip:matrix.org joined the room. | 14:50:28 |
| @wybpip:matrix.org left the room. | 14:50:28 |
| 2 May 2022 |
| @wybpip:matrix.org joined the room. | 02:45:56 |
| @wybpip:matrix.org left the room. | 02:45:56 |
| 1 May 2023 |
|  imlostlmao joined the room. | 18:21:34 |
| 8 May 2023 |
|  glownigger joined the room. | 16:29:56 |
| 22 Oct 2023 |
| noashh changed their display name from noashh-now-on-rocketchat to noashh. | 15:21:27 |
