Advertisement
Damelon

Nxt Core Dev Q&A 20-03-2016

Mar 20th, 2016
892
0
Never
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 18.34 KB | None | 0 0
  1.  
  2. Bas Wisselink [18:00]
  3. Welcome to the first Slack Q&A with the Core Devs.
  4.  
  5. [18:00]
  6. Anyone can post their questions in here and they will do their best to answer
  7.  
  8. [18:00]
  9. I would like to request of the devs that they say which question they are answering in their answer to avoid confusion
  10.  
  11. [18:01]
  12. The Q&A will last for an hour :simple_smile:
  13.  
  14. [18:01]
  15. OK, shoot :simple_smile:
  16.  
  17. Cryptkeeper [18:01]
  18. Hi guys! I've read about 1.8 and wondered where we lost the 2FA feature. It seemed to me that Petko was quite far with the development for this.
  19.  
  20. jean-luc [18:02]
  21. it is not a simple feature, and it required account transfer to be implemented too
  22.  
  23. [18:02]
  24. which turned out to be really complicated
  25.  
  26. [18:02]
  27. so, after 2.0, if really needed
  28.  
  29. Cryptkeeper [18:02]
  30. Account Transfer == Panic Button?
  31.  
  32. jean-luc [18:03]
  33. yes, in case an attacker got your password
  34.  
  35. Cryptkeeper [18:03]
  36. OK, ack!
  37.  
  38. bcdev [18:04]
  39. Are you working on the project full-time, or do you have some other major sink of time [dayjob, etc]?
  40.  
  41. Lionel Jeannerat [18:04]
  42. hi
  43.  
  44. jean-luc [18:04]
  45. I am full time
  46. 1
  47.  
  48. Lyaffe [18:05]
  49. I'm still keeping my day job for 2-3 days a week
  50.  
  51. jeff mcdonald [18:05]
  52. joined #general
  53.  
  54. Lionel Jeannerat [18:06]
  55. Hi
  56.  
  57. Martis [18:06]
  58. There was some roadmap for 1.8. Is 1.9 planned, and if yes, what features planed for 1.9?
  59.  
  60. jeff mcdonald [18:06]
  61. hi everyone
  62.  
  63. jean-luc [18:06]
  64. to do an FNXT asset distribution, we would need a hardfork, so this would be 1.9
  65.  
  66. Martis [18:07]
  67. so, 1.9 only for FNXT stuff?
  68.  
  69. Lionel Jeannerat [18:07]
  70. What is the goal of the road map ? Much nxters don't understand the vision behind the announcements ?
  71.  
  72. jean-luc [18:08]
  73. there may be a few minor fixes that require hard fork too, to go into 1.9, other than that, don't know yet
  74.  
  75. altsheets [18:08]
  76. Thanks for (re)implementing the http://localhost:7876&modal=send_money_modal ... etc. - it was one of my wishes; great, thx.
  77. Will make it easy to link from any webpage into the local wallet.
  78.  
  79. nxter [18:08]
  80. Hi There. Is it planned somewhere in the development roadmap to enhance the asset exchange and add new features to it?
  81.  
  82. Lionel Jeannerat [18:09]
  83. We were leader in the assets exchange but we lose our big advantage
  84.  
  85. jean-luc [18:09]
  86. anything that requires more work or a hard fork, after 2.0
  87.  
  88. [18:09]
  89. for UI only enhancements, if riker has time...
  90.  
  91. bummer gaycoin [18:09]
  92. joined #general
  93.  
  94. Websioux [18:09]
  95. hi
  96.  
  97. Lyaffe [18:10]
  98. We do have capacity for some UI features in case they make sense for 1.9. For 1.8 we are already introducing the desktop wallet which is a major enhancement which will probably breed more feature requests and ideas.
  99.  
  100. nxtswe [18:10]
  101. Hi!
  102. There has been a few misunderstandings regarding the dividend feature and that it does not show up in the transaction list. Is there anything planned to make this more user friendly?
  103.  
  104. jean-luc [18:11]
  105. I suggested adding a more prominent "view ledger" link on the dashboard, under recent transactions
  106.  
  107. [18:11]
  108. or even replacing the recent transactions with account ledger, or fit both
  109.  
  110. bummer gaycoin [18:11]
  111. great progress on nxt
  112.  
  113. nxtswe [18:11]
  114. sounds like a good idea to replace transactions with account ledger, that would solve it I think. thanx.
  115.  
  116. Lyaffe [18:12]
  117. The account ledger is not simple to read
  118.  
  119. jean-luc [18:12]
  120. I think one reason against that was that unconfirmed transactions would not show in account ledger
  121.  
  122. Lyaffe [18:12]
  123. The transaction list is more important for most users
  124.  
  125. jean-luc [18:12]
  126. and people expect to see them on top on the dashboard
  127.  
  128. Killakem TVE [18:12]
  129. Hi @jean-luc, @riker! I would first like to say, Thank You, for all the time and effort you guys dedicate to this project!! 2.0 is a very interesting concept indeed, I can fully understand the benefits and the effect it will have on nxt, which will of course be very positive. The main concern from people I have spoken with is assets, what protections will be in place to ensure the Asset markets don't have excessive downwards pressure from people selling assets for nxt.
  130.  
  131. altsheets [18:13]
  132. > account ledger is not simple to read
  133. what about designing ICONS for each type of transaction on the account ledger?
  134.  
  135. Lyaffe [18:14]
  136. @killakem: I think that making predictions about asset prices a year from now is not something we can base design decisions upon. NXT 2.0 also brings some advantages to asset issuer in the form of being able to trade the same asset on multiple child chains.
  137.  
  138. jean-luc [18:15]
  139. also, such selling pressure will exist mostly before the snapshot, but after that, markets should come back to normal
  140.  
  141. Lyaffe [18:15]
  142. @altsheets: its all about priorities
  143.  
  144. jean-luc [18:16]
  145. and we have the idea of doing a continuous snapshot, over a period of even few months, to minimize market impact
  146.  
  147. Lionel Jeannerat [18:17]
  148. When will be the snapshot?
  149.  
  150. Cryptkeeper [18:17]
  151. I have another question about the 1.8 changes: one of the new features is a "Simple server side plugin framework". Sounds interesting, could you elaborate what can be done with it?
  152. 1
  153.  
  154. jean-luc [18:18]
  155. the poll suggested 1-4 months from now, but of course we need to get 1.8 out first and then plan the hard fork
  156.  
  157. [18:18]
  158. so the start may be more like 2 months from now at least, since we need to allow people time before hard fork
  159.  
  160. [18:19]
  161. the plugin framework is for doing simple things in java, without having to patch and recompile NRS every time
  162.  
  163. [18:19]
  164. you can write your own class that does something when e.g. an account balance changes, and there are hooks to register this class with the NRS
  165. 1
  166.  
  167. Lionel Jeannerat [18:20]
  168. I have a important question: how can the community help?
  169. 1
  170.  
  171. Killakem TVE [18:21]
  172. Thanks guys! @riker Thats a useful feature indeed, we could have a sidechain for TVE and trade the TVE asset on our sidechain as well!
  173.  
  174. Lyaffe [18:21]
  175. The community can help a lot, Wiki documentation, support site, promotion with anyone who is willing to talk to you (edited)
  176.  
  177. Lionel Jeannerat [18:21]
  178. I have the feeling that the community is disconnected with the vision of the devs, how can we participate to the vision of future of Nxt
  179.  
  180. josenxt [18:21]
  181. Hi Devs, Thanks a lot for your job :smiley:
  182. Do you already know how often the prunning process will take place in 2.0? I mean if it will take place everytime the blockchain reaches a certain size, or the 1st Monday of every month, or...
  183.  
  184. Lionel Jeannerat [18:22]
  185. Much people ask me "what is the future of Nxt" and I can't anymore answer
  186.  
  187. [18:22]
  188. Because I don't understand the roadmap
  189.  
  190. jean-luc [18:23]
  191. pruning will be configurable, just like it is now for prunable messages and cloud data, a node can decide to store everything forever
  192.  
  193. [18:23]
  194. what the defaults should be, it is way to early to say
  195. 1
  196.  
  197. Cryptkeeper [18:24]
  198. LOL - when the hard disk is full, it's too late to prune :grinning: (edited)
  199.  
  200. jean-luc [18:25]
  201. one of the goals of 2.0, other than scalability, was to allow others to use the Nxt platform without necessarily using the NXT token itself, but still be a part of the same system, rather than starting their own cloned copy
  202.  
  203. nxter [18:26]
  204. Will aliases be global to all childchains?
  205.  
  206. Tosch [18:26]
  207. joined #general
  208.  
  209. Lyaffe [18:26]
  210. @ludom: I don't have a crystal ball, look at the blockchain usage trend https://www.google.com/trends/explore#q=blockchain - usage of blockchain applications will explode soon. We need to keep in the forefront and we will find our niche
  211.  
  212. Google Trends - Web Search interest - Worldwide, 2004 - present
  213. Explore Google Search trends with Google Trends.
  214.  
  215. Lionel Jeannerat [18:27]
  216. And what is our niche ?
  217.  
  218. jean-luc [18:27]
  219. aliases, I don't think they should be global
  220.  
  221. [18:28]
  222. but by default, when you are using the Nxt child chain, you will be seeing the aliases that exist on it
  223.  
  224. [18:28]
  225. to query the value of an alias on another chain, you would need something like a prefix, e.g. BTC.aliasname
  226.  
  227. [18:29]
  228. since nothing internally depends on aliases, I am not thinking about that now
  229.  
  230. Lyaffe [18:29]
  231. @ludom: I think that it can come from many different fronts AE, MS, Voting, phasing we have the best technology out there
  232.  
  233. Lionel Jeannerat [18:29]
  234. But we are not leader
  235.  
  236. [18:30]
  237. Because the fees are to high
  238.  
  239. Lyaffe [18:30]
  240. But we already voted about fees before 1.7 and the community decision was to leave them on 1 nxt (edited)
  241.  
  242. Lionel Jeannerat [18:31]
  243. Yes
  244.  
  245. [18:31]
  246. I came with a project of dedicated "voting system"
  247.  
  248. Lyaffe [18:32]
  249. Once we improve scalability we can reduce fees for the child chains
  250.  
  251. Lionel Jeannerat [18:32]
  252. ok
  253.  
  254. come-from-beyond [18:32]
  255. joined #general
  256.  
  257. Tosch [18:32]
  258. Hello guys! Thank you for the Q&A I am a bit late now and I hope I don't repeat questions. Actually I have many questions regarding childchains. And I will wait until more specs arrive. But kind of urgent for me to know how to continue with for example the mynxt.info website. How do you imagine such a service makes sense later? Taking the blockexplorer. Will I be able to display ALL childchains?
  259.  
  260. Martis [18:32]
  261. can child chain creators decide on child chain fees?
  262.  
  263. stephane gaudreault [18:32]
  264. joined #general
  265.  
  266. Cryptkeeper [18:33]
  267. I needed a while to understand the concept of Nxt 2.0, but now I think it's a great idea! :+1:
  268. IMHO one aspect isn't yet fully explained: how the child chains get their tx included into the fNXT blocks and who must pay whom for this in which currency?
  269.  
  270. jean-luc [18:34]
  271. transaction senders pay fees in native child chain currency, then anyone who wants to step in (although by default it may be the block forger) can take those fees, and pay in fNXT to the forger instead
  272.  
  273. [18:34]
  274. the min fee will be defined in fNXT
  275.  
  276. josenxt [18:35]
  277. How many transactions per second could NRS2.0 support?
  278.  
  279. [18:35]
  280. Would there be room for even more optimization in tps?
  281. 1
  282.  
  283. jean-luc [18:36]
  284. @tosh, it should be possible to display all child chains, why not
  285.  
  286. Tosch [18:37]
  287. cool. I thought maybe you are thinking about "private" vs "public" chains but there is no such thing?
  288.  
  289. Cryptkeeper [18:37]
  290. So there are forgers on the child chain and forgers on the fNXT chain? And the child chain forgers take the tx for "their" currency and includes it in fNXT chain for fNXT (or whatever it's called then)? (edited)
  291.  
  292. jean-luc [18:37]
  293. we can't have private chains, in the sense of content not visible, because all nodes need to validate all transactions
  294.  
  295. [18:38]
  296. yes, although I wouldn't call them forgers, besides anyone could do it for the child chains, regardless of balance, as long as they are willing to pay that fNXT amount in exchange for the child token amount
  297.  
  298. Lyaffe [18:39]
  299. @josenxt: the scalability depends on the usage pattern. Our best case scenario are not many very active child chains. In this scenario we can reach great scaling improvement perhaps 50:1 over the current scaling. I think it's too early to tell. We can later improve this further for sure.
  300. 2
  301.  
  302. Lionel Jeannerat [18:39]
  303. What about concurrence between childchains? If we reach the limit of TPS, some childchains will died because their transaction will not be validated?
  304.  
  305. jean-luc [18:40]
  306. those chains will have to pay more, to compete for inclusion in blocks
  307.  
  308. Websioux [18:41]
  309. Big picture : shouldn't we try to become the reference of crypto framework for web designers ? or are we trying to find a hit with a sudden lucky feature ?
  310.  
  311. Cryptkeeper [18:41]
  312. So if there is not much incentive to trade in "native currency" for fNXT, I guess the only "child chain forger" would be the creator of the child chain or some "operators".
  313.  
  314. Tosch [18:41]
  315. There will be different sort of childchains right? Some will have simple send, some will have the Asset Exchange, DGS etc. Would it be possible to integrate new functionality like solidity from ethereum in such a childchain? Would it be possible to have a childchain with own rules as long as the transaction that comes into the block with fNXT is valid?
  316.  
  317. nxt3d.net [18:42]
  318. there is some news about the DGS ? thank you
  319.  
  320. Fernando Ruiz-Tapiador [18:42]
  321. joined #general
  322.  
  323. jean-luc [18:42]
  324. yes, if you create a child chain and want to keep it running even if its token doesn't have real market value, such a creator would have to keep paying the fees himself
  325.  
  326. Lyaffe [18:43]
  327. @websioux: web designers ?
  328.  
  329. Lionel Jeannerat [18:43]
  330. Pinned a message. See all pinned items in this channel.
  331. jean-luc
  332. those chains will have to pay more, to compete for inclusion in blocks
  333. Today at 18:40
  334.  
  335. jean-luc [18:43]
  336. childchain with own rules, yes, but they must be a subset of what is possible
  337.  
  338. Lyaffe [18:43]
  339. @nxt3d_net: what are you missing ?
  340.  
  341. Cryptkeeper [18:43]
  342. OK, I guess you have all the edge cases covered. But my head is spinning! :stuck_out_tongue_winking_eye:
  343.  
  344. Websioux [18:43]
  345. @riker any business though the web
  346.  
  347. Lionel Jeannerat [18:43]
  348. But if there is not enough TPS for all the chain, it'll be a problem
  349.  
  350. jean-luc [18:43]
  351. e.g., with no shuffling allowed, or with only some accounts permitted to issue assets
  352.  
  353. Websioux [18:44]
  354. I should have say web business designer
  355.  
  356. Lyaffe [18:44]
  357. @websioux: I don't think we need to specialize on a specific feature. We need to provide the best tools for decentralized apps dev.
  358.  
  359. [18:45]
  360. Specific projects can then specialize on their domain
  361.  
  362. Martis [18:46]
  363. are there some plans to optimize and speed up blockchain download from scratch, if possible?
  364. 2
  365.  
  366. Websioux [18:46]
  367. ok good if this is the goal, stay general
  368.  
  369. jean-luc [18:46]
  370. the block size limits are not set in stone, if the hardcoded limits are reached, we can think about changing them, if the practical CPU processing limits are reached, this is already quite a lot of transactions, I wouldn't worry that far in the future
  371.  
  372. Lionel Jeannerat [18:46]
  373. The address of the childchains will be NXT-XXXX-XXXX-XXXXX ? Or they will have their own code ?
  374.  
  375. jean-luc [18:46]
  376. the secret phrase to public key to account number mapping doesn't change
  377.  
  378. [18:47]
  379. so accounts will be global, and will be able to have balance on multiple chains
  380.  
  381. [18:47]
  382. the NXT- is just a vanity prefix
  383.  
  384. come-from-beyond [18:47]
  385. Is it possible to create some kind of interface (similar to Java interfaces) that would allow to "attach" any platform as a sidechain? The interface is supposed to work in such a way that its complete implementation would be enough and Nxt core wouldn't need to know the nuances of the attached platform. If such an interface is possible, when could we get the documentation (ETA)?
  386.  
  387. nxt3d.net [18:47]
  388. @riker images, better listing... the firestorm bug relative to the wallet display into the virtual worlds was fixed and now we can fully use the wallet... but the thing that may interest the metaverse users is the marketplace in first... there is some dev on it? thank's
  389.  
  390. Lyaffe [18:48]
  391. @nxt3d_net: let's take it offline. PM me on the forum
  392.  
  393. jean-luc [18:48]
  394. attach an external platform? hm, not sure how exactly this could work...
  395.  
  396. brangdon [18:48]
  397. Do you think this is adequate to satisfy compliance requirements? If, eg, shuffling is not allowed on a business chain, but it still allowed on other chains the business's node is processing, won't the business still get into trouble if local law makes shuffling illegal? Are the businesses you've talked to happy with this?
  398.  
  399. jean-luc [18:49]
  400. what we call child chains are really transactions denominated in a different token, getting stored in their separate db schema, and optionally pruned differently, but they are still the basic Nxt transaction types
  401.  
  402. seccour [18:49]
  403. :squirrel:
  404.  
  405. come-from-beyond [18:50]
  406. Thx
  407.  
  408. Lyaffe [18:50]
  409. @brangdon: not every business will be able to use the public chain because of compliance issues
  410.  
  411. bcdev [18:51]
  412. Are there any plans for a scripting language a'la Bitcoin transaction scripts? (edited)
  413.  
  414. jean-luc [18:52]
  415. for such a business, a private clone will still be needed, but when based on 2.0 such clone will have the advantage of better scalability even if it runs a single child chain for that business only
  416.  
  417. Lyaffe [18:52]
  418. @bcdev: I don't think we should invest in scripting unless we find something very simple to implement. There are already several blockchains which specialized in this and we'll never catch up
  419.  
  420. Martis [18:53]
  421. I'll repeat my question, as it was not answered: are there some plans to optimize and speed up blockchain download from scratch, if possible?
  422.  
  423. Cryptkeeper [18:53]
  424. Pinned a message. See all pinned items in this channel.
  425. Lyaffe riker
  426. @bcdev: I don't think we should invest in scripting unless we find something very simple to implement. There are already several blockchains which specialized in this and we'll never catch up
  427. Today at 18:52
  428.  
  429. jean-luc [18:53]
  430. 1.8 is already as optimized as I can make it
  431.  
  432. altsheets [18:54]
  433. what about offering the peerexplorer bootstrap download as a choice in the installer?
  434.  
  435. jean-luc [18:54]
  436. for 2.0, of course it should be faster, as there will be fewer data to download, but more importantly much less processing to do
  437.  
  438. Lyaffe [18:54]
  439. @martis: when we have pruning in 2.0 you'll need to download less data
  440.  
  441. altsheets [18:54]
  442. that IS fast
  443.  
  444. Martis [18:54]
  445. ROGER :simple_smile:
  446.  
  447. jean-luc [18:55]
  448. not in the installer
  449.  
  450. [18:55]
  451. and we need a replacement for peerexplorer anyway
  452.  
  453. Bas Wisselink [18:55]
  454. We are already talking to crimi
  455.  
  456. Dave Pearce [18:56]
  457. Ummm....I may have reached a deal with Crimi to keep PE up.
  458. 3
  459.  
  460. Bas Wisselink [18:56]
  461. Chances are good we can keep PE going :simple_smile:
  462.  
  463. Dave Pearce [18:56]
  464. And....it's time to start wrapping up this Q+A, guys
  465.  
  466. [18:57]
  467. Shall we take one more question ?
  468.  
  469. nxter [18:57]
  470. what are the current estimated eta on 1,8 1.9 and 2.0?
  471.  
  472. altsheets [18:57]
  473. I have one more question:
  474. Which of the ​*far future*​ ideas of the http://www.nxttechnologytree.com do you personally find most exciting? (edited)
  475.  
  476. Lyaffe [18:57]
  477. @nxter
  478.  
  479. new messages
  480. [18:58]
  481. @nxter: 1.8 is probably 2-3 weeks away. 1.9 several month. 2.0 not sure
  482.  
  483. nxt3d.net [18:59]
  484. thank you for this useful meeting and informations, i hope will be more Dev Q&A in the future :simple_smile:
  485. 4
  486.  
  487. Lyaffe [18:59]
  488. @altsheets: for me I get excited when users are using my code. I don't get attached to specific features
  489. 1
  490.  
  491. Dave Pearce [19:00]
  492. I think there will be,....thanks, everyone
  493. 1
  494.  
  495. Lyaffe [19:00]
  496. thanks everyone
  497.  
  498. Martis [19:00]
  499. Thank you devs
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement