API tools faq
paste
Guest User

vite dev hr

a guest
Aug 29th, 2022
214
0
Never
Add comment
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 6.62 KB | None | 0 0
raw download clone embed print report
  1. Q (iMalFect) : Are there any plans for improving the soliditypp visual studio code extension? The "debugger" does look kinda old-style and I think you should do something like Ethereum Remix, would be easy to develop smart contracts like these. Also, can we expect an easy-to-see information when transaction is reverted? We have to click the "more" icon to see that the transaction has been reverted
  2.  
  3. A (Mike) : Yes, the debugger is actively being worked on (not by me). The next iteration will be a lot nicer (so it looks like, I haven't tried it yet)
  4.  
  5. ----
  6.  
  7. Q (iMalFect) : Also, is there any chance we'll see the debugger on JetBrains IDE's?
  8.  
  9.  
  10. A (Mike) : Very low chance we'll have a jetbrains debugger, I think we're focusing mainly on vs code
  11.  
  12.  
  13. ----
  14.  
  15. Q (iMalFect) : Also, are there any plans on fixing the documentation? I've reported some problems December 2021, and well. You didn't fix it yet.
  16.  
  17. A (Mike) : Yes, we have an internal doc that goes through a review by @Allen | Vite before publishing for the public. Maybe your suggestion got lost somehow, not sure. I think we should streamline that workflow
  18.  
  19. ----
  20.  
  21. Q (iMalFect) : May I see the new documentation? Happy to check it out, were the older docs reviewed by anyone?
  22.  
  23. A (Mike) : If the "new" docs are not published yet, they are still in our private repo
  24.  
  25. ----
  26.  
  27. Q (iMalFect) : By the way, how much % of the supply is currently held by ViteLabs
  28.  
  29. A: Waiting for Richard's reply
  30.  
  31. ----
  32.  
  33. Q (iMalFect) : Oh by the way, may I see the current list of active ViteLabs Gitcoin bounties? Wanted to complete something but still see the ones that were completed. eg. VitePay
  34.  
  35. A (Mike) : Thanks for bringing this up a second time. I will work with Gitcoin and make sure that this list is all up to date.
  36.  
  37. ----
  38.  
  39. Q (iMalFect) : Anyways, are there any plans to "dynamically" grow Vite? we've been kinda going "downstairs", 0.10$ => 0.02$ (obviously not gonna complain about the price, that's the market) also haven't seen much new in Vite itself recently
  40.  
  41. A (Mike) : We're talking internally about how to grow the NFT usage on Vite. Vite's unique architecture gives us an opportunity to improve the UX of NFTs on other chains
  42.  
  43. ----
  44.  
  45. Q (iMalFect) : True, also I know this is probably unrelated to y'all so sorry, but do you know what has happened to VitePunks
  46.  
  47. A (Mike) : For Vite Punks, I'm not sure what their progress is. I'm not involved in their development
  48.  
  49. ----
  50.  
  51. Q (iMalFect) : By the way, are you guys working on an NFT marketplace? It's true that Vite is an awesome platform for NFT's due to no fees.
  52.  
  53. A (Mike) : That's something we're discussing internally. There are a lot of directions it could go in
  54.  
  55. ----
  56.  
  57. Q (iMalFect) : Who's working on the Vite mobile app?
  58. I feel like it's been kind of "ignored", nothing new recently.
  59. When can we expect dark mode in the Vite app?
  60.  
  61. A (Mike) : That's for @Blackey | Vite to decide. My work is focused on the ViteBridge frontend, Vite Express, and our upcoming wallet extension
  62.  
  63. ----
  64.  
  65. Q (iMalFect) : Also, are you guys planning on helping promising vite projects grow by giving them funds to list on exchanges, and etc.?
  66.  
  67. A (Mike) : We've talked about that and are considering it, I think it will happen, I'm just not sure for which projects
  68.  
  69. ----
  70.  
  71. Q: Whats prioritized right now? (KaffinPX)
  72.  
  73. A (Mike) : We just hired a new dev @jplew who will be ramping up NFT stuff on Vite. Wes is working on OpenZeppelin compatibility, I'm working on a lot of frontend stuff, the other devs are doing stuff with ViteBridge and the core protocol
  74.  
  75. KaffinPX : Thats definitely not a good prioritization
  76. Firstly - Assets are native on Vite, NFTs should be native too because staking for all of NFT contracts will be pain
  77.  
  78. Mike (Vite) : Yes we are talking about native NFTs
  79.  
  80. KaffinPX : Secondly- Improvement of core protocol should start with economics of Vite.
  81. Like currently contract creation fee is constant, it should be based on contracts size + as example Vites supplys 0.0001% so can increase with inflation. Same thing with token minting fees
  82.  
  83. Mike (Vite) : Good idea, idk if we'll change existing fees, but there will definitely be more burn mechanisms with native NFTs, as an example
  84.  
  85. KaffinPX : Next thing- If contract drains all quota, all receivable txs should fail otherwise it creates a way to make network spam itself
  86.  
  87. Mike (Vite) : Yeah, that's another thing I've seen talked about internally. I don't work with the Go codebase though, so can't talk much more about spam prevention
  88.  
  89. KaffinPX : Also maybe a backdoor on next hard fork for burning VitogeSBP LMAO
  90.  
  91. Mike (Vite) : I think we're trying to build an dapp ecosystem that applies the rules fairly/transparently to everyone, so doubt this will happen lol
  92.  
  93. KaffinPX : And Finally-Move ViteX admin controls to a Multisig contract&wallet, also when governance system, You vote by VITE for proposals, For creating a proposal you need to lock some Vite(Maybe 10k Vite), if you get VETOd your Vite gets burned
  94.  
  95. Mike (Vite) : This isn't on our bucket list yet, or maybe ever. It sounds like something you could build tho
  96.  
  97. KaffinPX : So can control Vite variables, Like constant fees of ViteX
  98.  
  99. Mike (Vite) : Vite isn't at the scale yet where that tool would be warranted
  100.  
  101. ----
  102.  
  103. Q (KaffinPX) : When first metaverse on Vite?
  104.  
  105. A (Mike) : idk, but it'd be cool if we had an mmorpg that used Vite's native assets (and potentially native nfts)
  106.  
  107. Q2 (KaffinPX) : Wen supporting first metaverse project of Vite lmao
  108.  
  109. A2 (Mike) : When a legit team asks Vite Labs for a grant I guess lol
  110.  
  111. (KaffinPX) : Thats very complicated
  112. Vitelabs requests video chats for everything
  113.  
  114. (Mike) : Oh, yeah that's a new policy. It really weeds out the ppl who aren't serious
  115.  
  116. (KaffinPX) : Also weeds out the people who are serious
  117. Thats not best way to filter projects
  118.  
  119. (Mike) : Possibly, we could always change. Just trying new things out.
  120.  
  121. ----
  122.  
  123. Q (KaffinPX) : Also some technical suggestions - Stop webpacking Vite.js after installation, it makes harder to debug problems
  124.  
  125. A (Mike) : Ikr, that's another thing we have to work on. we'll probably switch to esbuild
  126.  
  127. ----
  128.  
  129. Q (KaffinPX) : Another thingy- PRIZE scam on ViteX, Vitelabs can hide pairs on frontend but they dont, why?
  130.  
  131. A (Mike) : doing that kind of stuff is controversial, so we avoid taking that kind of action. Seems like a lose-lose situation imo
  132.  
  133. (KaffinPX) : But VITOGE pairs?
  134.  
  135. (Mike) : idk, but my time is better spent coding and building stuff than making a decision on censorship.
  136.  
  137. ----
  138.  
  139. Q (KaffinPX) : Also any news from VitePassport extension? lol
  140.  
  141. A (Mike) : It's very close to being publicly released. Still testing/reviewing it internally
  142.  
  143.  
Add Comment
Please, Sign In to add comment
Public Pastes
We use cookies for various purposes including analytics. By continuing to use Pastebin, you agree to our use of cookies as described in the Cookies Policy.  OK, I Understand
Not a member of Pastebin yet?
Sign Up, it unlocks many cool features!