As promised last week in my previous post, here’s an update on the “frontend” work we’ve been working of for the past few months.
Block Explorer User Interface
The block explorer project was created because I wanted us to have an fast, easy-to-deploy, open source block explorer that could be hosted in a decentralized manner.
Our team has accomplished our main goals on this project, so I recently approached @mcfarhat to take over development of the project (his team had already been contributing to the project for a while).
As part of this, one of our UI programmers will be joining his team full time and one of our backend programmers will also assist them part-time during the transition period. If you haven't already voted for his proposal, I highly encourage you to do so:
https://hive.blog/hive-139531/@mcfarhat/hive-dev-proposal
New features and functional improvements
- The block explorer is nearly ready to be released. Here is a MR covering most of the new work: https://gitlab.syncad.com/hive/block_explorer_ui/-/merge_requests/424
- Support for account value displayed in the wallet card: https://gitlab.syncad.com/hive/block_explorer_ui/-/merge_requests/442
- Better support for mobile platforms such as cellphones and tablets
- Witness schedule page: https://gitlab.syncad.com/hive/block_explorer_ui/-/merge_requests/411
- Theme support improvements (e.g. dark theme)
- Security updates: https://gitlab.syncad.com/hive/block_explorer_ui/-/merge_requests/413
Bugfixes
- Fixed bugs related to VESTS presentation using HP values
- Improved copying a operations on block page (to get their original content)
- UI improvements: https://gitlab.syncad.com/hive/block_explorer_ui/-/merge_requests/422https://gitlab.syncad.com/hive/block_explorer_ui/-/merge_requests/376
For GUIs, a picture is worth a thousand words, so here’s some screenshots:
Denser: social mediasite for Hive (replaces condenser)
New features and functional improvements
- Improving support for wallet related functions
- Covered blog functionality fully matching condenser’s feature set
- Using Optimistic UI patterns to show user activity in the application, then confirmed or rejected by API node
- Support for oauth server to allow chat integration
- Reduced resource usage
Bugfixes
- Improvements in the post editor: https://gitlab.syncad.com/hive/denser/-/issues/486 https://gitlab.syncad.com/hive/denser/-/issues/488 https://gitlab.syncad.com/hive/denser/-/issues/482 https://gitlab.syncad.com/hive/denser/-/issues/487
- Fixes related to post rendering issues
- Posts pinning is handled correctly
Here's a screenshot of Denser (it looks very much like Condenser, but it is really entirely new software!):
Transaction inspector: a new tool for analyzing transactions
Transaction inspector is a new application which visually renders info about a Hive transaction to help solve authority & validity problems. This tool is especially useful when trying to determine why a transaction was rejected by a blockchain node.
The codebase for the transaction inspector is under intensive development, although it works already for most of cases. Lately we decided to do some internal refactoring of the code to achieve two goals:
- Improve regression testing to simplify preparing and verifying specific transactions
- Make it easier to import the app’s algorithms for performing transaction processing into 3rd party applications.
Near term improvements include:
- Add algorithms to test for bugs in transactions, so that applications can verify they’ve constructed valid transactions.
- Implement a transaction/operation binary view which will help analyze and show how a transaction has been serialized internally in the blockchain. This could help to solve issues related to the dreaded “missing authority” errors, since a user will be able to see the transaction contents in the "Hive blockchain" language. This should especially be useful for Hive developers.
Here’s some screenshots of the transaction inspector:
Clive: a TUI and CLI wallet for Hive
Clive is being designed as a wallet for “power users” who want to have high security and full control over the way they create Hive transactions. As such it will have much more fine-grained control on how a Hive transaction can be created and signed than typical wallets. It will also support advanced features such as easy offline signing for cold wallets.
Clive comes in two versions: a command-line version and and a more friendly “terminal user inteface” (TUI) version which is similar to a graphical user interface, but can run on a terminal console that doesn’t support graphics.
Clive is written in python and we’re also using it to test and improve the python version of Wax.
New features and functional improvements;
- Support for tracked/known/exchange/bad account list to make blockchain transfers safer. Known accounts are accounts you've made transfers to in the past. Exchange accounts are specially marked because they often require a special memo and only take specific currencies. Bad accounts are suspected/known "phishing" accounts.
- Easier to switch to a different working account (the account used for transaction creation)
- Significant improvements in application TUI to simplify its usage
- Developed simple startup script to simplify application start
- Support for custom json & recurrent transfer operations
A detailed view of the changes can be found in the release notes below:
- https://gitlab.syncad.com/hive/clive/-/releases/v1.27.5.16
- https://gitlab.syncad.com/hive/clive/-/releases/v1.27.5.15
- https://gitlab.syncad.com/hive/clive/-/releases/v1.27.5.14
- https://gitlab.syncad.com/hive/clive/-/releases/v1.27.5.13
- https://gitlab.syncad.com/hive/clive/-/releases/v1.27.5.11
I didn't include any screenshots for Clive this time, due to the number of planned changes to the UI, but I will add some to my next post.
What’s next for the UI apps?
The block explorer API and UI will be officially released as part of the next update to Hive API nodes (planned for December). This means that every API node by default will supply the block explorer API (which can be used by any Hive block explorer) and they will also be able to easily deploy their own copy of the block explorer UI, so we should have very decentralized hosting of the block explorer.
Denser is also getting closer to release, but I think it will be released after the Hive API node release. My best guess is somewhere in 2nd quarter of 2025. Currently most of the remaining work is related to wallet features.
The Transaction Inspector is targeted at a smaller audience (primary developers and power users). As such it is already useful for developers who want to analyze transactions, and soon it should be possible to easily incorporate it’s functionality into other applications.
Because of the many changes and improvements currently being simultaneously made to Clive, the release date is a little difficult to predict (a lot of testing will be necessary), but I’m hopeful that it will also be officially released in December, but probably after the Hive API node release.
Seems Promising.
GG, keep up the good work.
Quick side conversation - do you think there could be a 100% HBD reward option in Hive's future?
Thanks :)
This would completely side step the 13 week power down.
Exactly.
Yeah, I don't like the 13 week power down, it's too long.
Probably a good thing for already locked stake to avoid DPOS vote weight collapse, but for earning to pay for goods it's lame imo.
Actually there's such an option. It's called
transferand if your content is so good that people would send you HBD then good for you :-)Despite exclusively posting to Hive this doesn't seem to happen, lol.
I don't think there would be any negative effect to Hive by allowing 100% HBD post rewards, if anything it'd encourage me to post more frequently.
You posting more frequently is neither positive nor negative for Hive.
You dumping your rewards instantly is negative for Hive.
Powering up is positive for Hive.
I've got no plans to tinker with the reward options, but it isn't that hard to exchange Hive for HBD on the internal market.
True, it just takes so long to power down to do so, makes it tough to spend earnings on goods in a timely manner imo.
Looks fantastic and shows a lot of effort behind it. Wishing you continued success!
Testing that rightnow, first time i know about it. Hah. !BBH !LUV
Out of curiosity, which app are you referring to?
Random, just realised looking through the screenshots I missed checking who produced block #90m.
it was @therealwolf
!PIZZA
I might have missed this, but have you all been able to work on the multi signature changes that are required for @vaultec and VSC. I can’t remember what those changes are called but I remember him being that up about 10-12 months ago.
He's asked us to support a new signature type (BLS) which allows for a more compact multisig. It's not strictly needed for VSC, IMO, although it would be helpful for VSC when creating multisigs for managing Hive assets (specifically Hive and HBD) and they definitely want it.
We haven't worked on it yet, but making changes to signature handling is the last big thing on the list of things we're hoping to add to hived in this release.
I've done work on how I want to change the signing algorithm in general, but I haven't looked much into the BLS aspect yet. The main issue is the other guy I want to work on this issue with has been tied up with another high priority task, but he should be free soon, then we'll attack the issue together.
But I'm not 100% sure yet we'll be be able to get any of the changes to signature handling into this hardfork. If not, that means we'll need to make the next hardfork sooner, so I'm still vaguely hopeful we can get it in.
I'd love to see this implemented! We are aiming to launch VSC mainnet in early 2025, so if we can get BLS support ahead of time that'll make our job much easier and the network more secure.
Hi, @vaultec,
This post has been voted on by @darkcloaks because you are an active member of the Darkcloaks gaming community.
Get started with Darkcloaks today, and follow us on Inleo for the latest updates.
Thanks for the work @blocktrades and team!
One question why are you supporting buildawhale who's downvoting my original work and others
It doesn't make any sense buildawhale is downvoting good content
Please stop supporting buildawhale as it makes Hive look like some sort of scam
It does not seem to be an easy task... But what a pleasure that we have very professional people working so that we can continue working in this family ❤️
God keep blessing this hard work you have achieved! 🙏
The Hive.Pizza team manually curated this post.
$PIZZA slices delivered:
@danzocal(5/10) tipped @blocktrades
Join us in Discord!
Congratulations @blocktrades! Your post has been a top performer on the Hive blockchain and you have been rewarded with this rare badge
You can view your badges on your board and compare yourself to others in the Ranking
If you no longer want to receive notifications, reply to this comment with the word
STOPCheck out our last posts:
Can the victims of scam get their money back? Yes, if you have fallen victim to scam from an unregulated investment platform or any scam at all then are eligible to recover what was stolen from you and this can only happen if this is reported to the right people. With the right approach and with evidence, you will get what you lost back. Those behind these unregulated platforms will likely want to sell the idea that what happened to your investment was an unfortunate occurrence when in reality what happened was theft via elaborate means. If you are a victim or you know any one who is a victim of these occurrences, you should know there are people who can help you. Simply contact email: RamsayMacDonald @ Consultant. com / WHATSAPP ; +1 (603) 702 ( 4335 )
just the way it is in that bracket. It is never too late if you have the right information, your sanity can be restored.
I'm disappointed in block trades