Jump to content

Halo-Shannon

Halo Platform Leadership
  • Content Count

    49
  • Joined

  • Last visited

  • Days Won

    6

Halo-Shannon last won the day on October 1

Halo-Shannon had the most liked content!

Community Reputation

18 Good

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Halo-Shannon

    Dex Version 0.9.0 Beta

    This version marks the first beta version. There are some unstable items within this, but they will be identified more clearly with user testing. Expect at least two more beta version before production version is released. Before production we will release a beta-final version. That has all polish done, and any future updates would be for hotfixing bugs only, no new features. Change Logs: Dex Frontend - Removed all prisma subscriptions - Added pusher pubsub - Subscriptions are fixed and live data all comes through now - Added landing page with statistics on tokens - Improved order book aggregate algorithm to be more performant - Drastically reduced application memory consumption - Trading View volume fixed - Trading View wicks fixed - Sidebar ticker is now live updated - Trading View now pulls live data from pusher - Trading View grabs exact 30 second intervals - Drastically reduced amount of data sent with each updated - Fixed clicking order populating order form - Fixed balances subscription - Fixed trades subscription - Fixed user orders subscription - Fixed creating orders - Fixed cancel order subscription - Fixed balances page not updating correctly - Fixed order matching - Fixed issue where dex would not know if user is buying or selling when making a trade Dex Backend - Faster order and contract event processing - Publish live events to pusher - Multi-threaded processes for watching contract - Improved prisma data storage - Clustered public API and load balanced - New message types of live data - New ticker format for 24 hour moving 30 second frame - Fixed ticker volumes and wicks for trading view to consume - Fixed data to be referenced by token number and not token address
  2. Halo-Shannon

    When I click Education.....

    It’s not open to the public yet, it was empty and I didn’t want it open until there was actual content in there. Which it seems Scott W has been adding stuff to it. So I’ll open it up tomorrow when I’m in the office.
  3. Halo-Shannon

    Masternodes Version 2.4.0

    Changelog: Fixed bug that prevented withdrawing rewards from watched nodes Fixed bug that caused a maximum of 5 sell orders to show on expanded sell orders Expanded sell orders now properly sorted by lowest pricePerShare Withdraw all and multi-select sell order purchases now use a single batch request Fixed bug in private join dialog that sometimes caused invites to not load correctly Fixed bug that sometimes caused masternodes to load twice Added dialog for withdraw all that displays total rewards to withdraw and rewards for each masternode
  4. Halo-Shannon

    Featherlite Version 1.1.1

    New version of featherlite is available for download. Please visit https://www.haloplatform.tech/downloads.html to get it. Changelog: Use app props and v-content instead of absolute positioning Remove extra scrollbars Remove whitespace between account status and main content Account status now wraps properly in narrow windows Cleaned up CSS selectors bugfix: Sometimes full node crashed the client, doesn't happen anymore feature: Support for batch transaction for dapps and a loading UI for it chore: Updated PP and ToS feature: Added a nice animation on client startup MD5: MD5 (feather-fedora-client-1.1.1.x86_64.rpm) = d35813ce209d85b49b583bbf744cf018 MD5 (feather-linux-client-1.1.1-x86_64.appImage) = 6acd9948b86ecfe93175a4c13fd1a09f MD5 (feather-mac-client-1.1.1-x64.dmg) = 2871c6858562310a016a55ae722285dc MD5 (feather-ubuntu-client_1.1.1-amd64.deb) = 4b18f15950dda262ad0e7027c3e5964b MD5 (feather-windows-client.Setup.1.1.1-x64.exe) = f6b58f2945d5f02aa256d669b9e176b4 MD5 (upload.sh) = 88e1d36674beea1ad4aea6108d7f3e9b
  5. Halo-Shannon

    Dex Version 0.4.0 Alpha

    Change Logs: - Changed alignment of sell orders - Resized the new order card to take up less space - Added contextual colors for buying and selling in the new order card - Added 8 decimal places to display data for the order book - tradingView replaced AmCharts for main chart on exchange - resolution and symbol changing updates - production config updated for static files relating to tradingView - Updated Balances page to now show wallet balances outside of dex. Also added some coloring to page to make it less boring
  6. Halo-Shannon

    DEX Contract Version 0.1.0 Beta 1

    We just pushed the Beta 1 version of the contract to the testnet chain. No changelog as it would be a mile long at this point. Will track changes from here on out. Upon public full release, we will release source of contract.
  7. Halo-Shannon

    24 Hour Block Rewards

    you are better at posting these than I am at posting reward payouts ?
  8. Halo-Shannon

    Top Menu - Feather

    depends on operating system, but we can look into this.
  9. Halo-Shannon

    Exchange

    You are hitting it on the nail there. We are working towards that exact thing!
  10. Halo-Shannon

    Exchange

    Hey there! Thanks for coming and asking, as those are very valid questions. I cannot answer the question about HALO being listed on an external exchange, however, I can address the rest of the question. First, I'd like to explain how we do our processes internally, and how that affects releases. Because of the nature of software and software development, there are always unknown factors. These unknown factors or edge cases can be a really big thorn in developers sides. Since these edge cases exist we as a company policy do not release any product directly from development into a live environment. So when we make an announcement that something will be live by X date then it is assumed on our end that this means live on a testnet or alpha/beta period. That being said, the plan was always to release to testnet first and not to mainnet. Secondly, we believe that end users have a say in how our applications flow, handle, and feel. This is why we release software as an alpha or beta state to testnet. This is not only to have the community help us find edge case bugs, but to also give us feedback on the interface and user experience. We take that feedback and use it to build a better and more refined end product. In case you are not aware we define four stages of an application when in development here at Halo Platform Development - This is purely internal development and most of the time not very transparent as a lot of things change and go back and forth. The entirety of the code base could change if we have a tech change or a hard blocker towards a route we were taking. Alpha - This is an unstable, bug filled, testnet release meant to give the initial feel of the platform and to have community help to refine it. This release does not particularly reflect what the end product will be. Beta - This is a more stable release to testnet. We will have addressed initial community concerns but continue to refine the platform. This release better reflects the end product. Production - This is a stable release to mainnet that is the end product. The answer to the question of "When will it be ready for live mainnet use" is... when it is ready. We will commit to doing often and continuous releases to fix issues and bugs as they appear, as well as add polish. The system for depositing eth is still not deployed to testnet but we hope to deploy it this week in its alpha state. Currently, I still view the dex as Alpha as there are rare issues with WebSockets that we need to track the bugs down and figure out how to eliminate the case were events are propagated properly. Now to answer what happened and why was it late, that is a bit easier to answer. We scheduled to launch to testnet on August 15th, and we successfully launched on August 16th. The reason that it was a day late was two-fold. We had the WebSocket issue that was preventing event propagation but it was much much worse. Systems that had been working in development for a while all of a sudden stopped working. (This happens in software development, it's called a development regression). We worked to finish fixing this and we were confident in fixing it. We finally found some major issues and had them resolved on the 15th of August. However, at this time it was well into the day (Late at night for our developers). We made a humane decision for the sake of our developers and community. We decided to not deploy until we had let our developers off for the night and come back in the morning with fresh and rested minds. This was to prevent any sudden issues from exhaustion from popping up during deployment. All in all, it took us a few hours to fully deploy and get all of our code moved through our release cycle, and so we released late afternoon on the 16th of August. I know I went into a lot of detail, and probably too much detail. However, I wanted the community to have all the facts and to understand how our processes work. If you have any further questions on this please don't hesitate to ask. Thanks, Shannon
  11. Halo-Shannon

    Taking care of business

    It is only going to get better!
  12. Halo-Shannon

    Async Iterators and GraphQL awesomeness!

    This blog post here goes into iterators quite a bit more. http://blog.cipherhack.com/2018/07/10/symbols-iterators-iterables-generators-explained/
  13. Halo-Shannon

    Marketplace Buy section

    So similar to an exchange then. Maybe we could do something in the future on the DEX regarding this.
  14. Halo-Shannon

    DEX Version 0.3.0 Alpha

    Change Log: Fixed subscriptions for order book Fixed price chart display issues Added validation to withdraw/deposit You can now see your wallet balance when depositing/withdrawing funds into/out of the DEX Fixed sorting of Buy Orders Improved performance of Buy/Sell Order tables
  15. Halo-Shannon

    What If?

    That fix is coming. Hmmm. Future versions will allow you to terminate directly instead of through us... SO... this might be possible to auto combine. Or we could structure a batch transaction to do that.
×

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue. - Please review our other terms and privacy polices here: Terms of Use and Privacy Policy