proposalPosts.js 6.2 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180
  1. const posts = [
  2. {
  3. threadId: 3,
  4. text: "Our first valid proposal, in this testnet. \\m/",
  5. id: 1,
  6. },
  7. {
  8. threadId: 6,
  9. text:
  10. "Tokens minted [here](https://testnet.joystream.org/#/explorer/query/0xe649437a8e4142f353d473936f5495e276de8f5d3f6886c8bf70c811812a66e8)\nand transferred over the next blocks.",
  11. id: 2,
  12. },
  13. {
  14. threadId: 7,
  15. text:
  16. "This has been cancelled as we can just repurpose the existing category for Joystream bounties for this purpose.",
  17. id: 3,
  18. },
  19. { threadId: 8, text: "Sounds good to me!", id: 4 },
  20. { threadId: 8, text: "Yup. Same here!", id: 5 },
  21. { threadId: 8, text: "Approved! :)", id: 6 },
  22. {
  23. threadId: 15,
  24. text:
  25. "I will give some percentage of the rewards to @tomato for creating the report template and @nexusfallout/Finnyfound for trying to help me :)",
  26. id: 7,
  27. },
  28. {
  29. threadId: 15,
  30. text: "😊 Thats okay. I was not able to do much work anyway.",
  31. id: 8,
  32. },
  33. { threadId: 15, text: "Hey, you deserve all the tokens! Great work!", id: 9 },
  34. {
  35. threadId: 17,
  36. text:
  37. "PS: Typo on Report Generator Report -> Council Report Generator\n\nIf you want to find more information about the Council Report Generator you can check the PR here:\nhttps://github.com/Joystream/community-repo/pull/29",
  38. id: 10,
  39. },
  40. {
  41. threadId: 19,
  42. text:
  43. "Hi betilada, welcome to the community. This amount sounds fair to me and I'll be voting to approve! If the proposal is approved I look forward to seeing some of your videos!",
  44. id: 11,
  45. },
  46. {
  47. threadId: 19,
  48. text:
  49. "Hi @betilada, welcome!\n\n\nIs really great to see new content in Joystream so I will approve! \n\n\nThe amount you requested seems good to me.",
  50. id: 12,
  51. },
  52. {
  53. threadId: 21,
  54. text: "I suggested 40 slots but I can agree with 35 :)",
  55. id: 13,
  56. },
  57. {
  58. threadId: 21,
  59. text: "Sorry I just saw your post, we really need that Telegram bot back!",
  60. id: 14,
  61. },
  62. { threadId: 25, text: "Seems good! ", id: 15 },
  63. {
  64. threadId: 27,
  65. text: "I like the ideas, it should help to keep things organized!",
  66. id: 16,
  67. },
  68. {
  69. threadId: 29,
  70. text: "PS: Typo on Council Generator Report -> Council Report Generator",
  71. id: 17,
  72. },
  73. {
  74. threadId: 31,
  75. text:
  76. "For KPI 3.3-Appoint New Council Secretary,the payment is $50,As the price now,it's about 1.01M tjoy,isn't it?",
  77. id: 18,
  78. },
  79. {
  80. threadId: 30,
  81. text: "For KPI 2.2 Council report,the payment is $0,isn't it?",
  82. id: 19,
  83. },
  84. {
  85. threadId: 31,
  86. text:
  87. "Hi @anthony, the $50 is the rewards the council receives for completing the KPI, the KPI itself says `The Council informally appoints a Council Secretary through a spending proposal and pays them an appropriate rate for their responsibilities.` I put a similar amount for the past council sessions and we have passed this KPI.",
  88. id: 20,
  89. },
  90. {
  91. threadId: 30,
  92. text:
  93. "@anthony the council reports are mandatory, so there is no payment. It is a pass/fail for the council. When there is work for the council to do, there's nothing stopping people from creating spending proposals for completing the work. It's up to the council to vote on the proposals as they want to.\nThe KPI rewards are explained here: https://github.com/Joystream/helpdesk/blob/master/tokenomics/README.md#council-kpis",
  94. id: 21,
  95. },
  96. {
  97. threadId: 32,
  98. text:
  99. "From what I've seen in the test channel it looks like the bot does just about everything it used to. I can't judge the coding myself though.",
  100. id: 22,
  101. },
  102. {
  103. threadId: 35,
  104. text:
  105. "A small correction: For example, the storage lead has an `agreed payment of $35 per week`, but this is currently an `actual payment of $34 per week`",
  106. id: 23,
  107. },
  108. {
  109. threadId: 34,
  110. text:
  111. "This spot check includes this `at this time the Curator Lead has opted to not recieve payments (this was communicated on Telegram)` which is wrong. It is contradicted by the payment information which is correct.",
  112. id: 24,
  113. },
  114. { threadId: 34, text: "Great work!", id: 25 },
  115. {
  116. threadId: 35,
  117. text:
  118. "I approve this changes but we really should think about cutting the slots for the validators, since this should increase the reward of each validator, right?\nAs reported in Telegram it seems that validators are not getting enough tokens to compensate for the cost of the servers, which will increase in the future, with the chain size increasing.",
  119. id: 26,
  120. },
  121. {
  122. threadId: 35,
  123. text:
  124. "On top of this is a role which is a bit difficult to control the payments, since it depends in the amount in stake.",
  125. id: 27,
  126. },
  127. {
  128. threadId: 35,
  129. text:
  130. "@freakstatic I think this is because a lot of validators don't have a large amount of stake, so it is easy for a nominator to put backing behind the validator which reduces the validator's rewards a lot. You can see this on the targets page, where the ratio of `own stake` : `total stake` is as high as 1:10.",
  131. id: 28,
  132. },
  133. { threadId: 35, text: "Interesting I didn't know about that", id: 29 },
  134. { threadId: 33, text: "You are doing great job @tomato", id: 30 },
  135. {
  136. threadId: 36,
  137. text:
  138. "According to JS Team burning of tokens will not change the value of tokens.",
  139. id: 31,
  140. },
  141. {
  142. threadId: 36,
  143. text:
  144. "@nexusfallout it appears correct. If tokens are burned then it shouldn't affect the token value.",
  145. id: 32,
  146. },
  147. { threadId: 36, text: "Totally agreed ", id: 33 },
  148. {
  149. threadId: 45,
  150. text:
  151. "I'm resubmitting this because the last proposal failed due to low council mint capacity",
  152. id: 34,
  153. },
  154. {
  155. threadId: 47,
  156. text:
  157. "I forgot to include my github link, here it is: \nhttps://github.com/freakstatic",
  158. id: 35,
  159. },
  160. {
  161. threadId: 47,
  162. text: "Thank you for stepping up! The community appreciates it! :)",
  163. id: 36,
  164. },
  165. { threadId: 57, text: "This is a very clear report thanks @tomato.", id: 37 },
  166. {
  167. threadId: 58,
  168. text:
  169. "Hope it will be more heavy role once Atlas is live. Waiting for that.",
  170. id: 38,
  171. },
  172. {
  173. threadId: 60,
  174. text:
  175. 'I forgot to note that "valid proposals" just means all proposals (including expired proposals) that were not cancelled or withdrawn.',
  176. id: 39,
  177. },
  178. ];
  179. export default posts;