Frontend for hive-engine.com
VSCode + Volar (and disable Vetur) + TypeScript Vue Plugin (Volar).
See Vite Configuration Reference.
npm install
npm run dev
npm run build
Lint with ESLint
npm run lint
Hive-Engine node software
Home Page: https://hive-engine.com
License: MIT License
Frontend for hive-engine.com
VSCode + Volar (and disable Vetur) + TypeScript Vue Plugin (Volar).
See Vite Configuration Reference.
npm install
npm run dev
npm run build
npm run lint
Idea from stoodkev:
On Hive internal market you can make a transaction like this :
https://hiveblocks.com/tx/29184b361fe8eceaaeac44d38e1dbb807d4e7ee5
Basically saying I want to sell all of this amount of HIVE, and cancel it if the result is not at least this amount of HBD
That makes it possible to define a kind of slippage on the market buy or market sell.
That would be super helpful because as it is, we can only implement "soft slippage" based on a market estimate at a given time, but we can't make sure that the slippage would be respected.
There exists no test for witness meeting missedRoundsInARow
and a new witness being selected. One should be created.
Should have an easy way to see total amount staked rather than having to calculate it.
Right now, all witnesses involved in a round get rewarded. We might potentially want to change this to only pay out the one witness who produced the round, and increase the amount they get by a factor of top witness count. In the long term, it should even out to being the same amount paid out to the witnesses.
In some cases, auto node switching doesn't work. It's based off the dhive implementation, so looking at the upstream codebase might be necessary.
transferOwnership emits no success message. It also emits no error when the NFT doesn't exist. This makes the outcome unknowable as pass and fail are both silent. For recent transactions, checking against an engine api or attempting a transaction can confirm the outcome. This workaround is not effective for historical data
example: https://he.dtools.dev/tx/c1d0a25188dd5a3c6fc8b406cde9caa64cef59d0 that particular NFT is not for sale, but does not emit an error
url: "https://engine.rishipanthee.com/blockchain"
params:
{"jsonrpc":"2.0","id":1,"method":"getTransactionInfo","params":{"txid":"0ce321d8f434c89ce0d8ef335126228b6e2d6811"}}
Customjson returns this txid 5cdf10b629cbf2d148d416d0f41aa6be7625b806
. I have batched multiple actions inside the same json to get around the engine limits. When fetching the result using the transaction id received from the customjson, the above api call returns null. The call needs to be modified as txid-0
, txid-1
for each batched action.
An alternate route that provides info for the entire transaction would be helpful.
RPC calls that take longer than an arbitrary number of ms(defined in config) should be killed and the mongo query killed too with a request took too long error message
There exists a silent fail condition on the nftmarket contract: https://he.dtools.dev/tx/b6cb80d68027aa5dbc600ef4a786ee67b3e7e2e1-0
That should be fixed.
The witness actions script should have tests to ensure it's functionality hasn't been broken.
Backup witnesses get selected less often than regular witnesses, and to compensate them for that, Hive pays them at an increased rate of 5x of T20. Engine should consider doing the same as backups earn a lot less than T20 as of now.
Wanted to start a discussion to see if anyone has ideas on how to improve the reliability of the RPC server.
The recent issues with batch requests caused the behavior where the RPC server stops responding and does not auto-recover. PM2 does not detect the issue and does not restart the service automatically. The node operator has to notice there is an issue and go call pm2 restart. Not ideal when it happens in the middle of the night.
How can we make it more resilient? Can the node detect the problem and restart itself? Currently, the death of the RPC server does not crash the whole service, so PM2/docker cannot know if it needs to be restarted.
Maybe needs more investigation to understand why the server stops responding. without throwing exception
When attempting to start a node for the first time syncing from genesis, with no data, and disabling light mode in the config, the following error occurs:
Can't switch from a node, which was previously a light node, to a full node. Please restore your database from a full node dump.
For example in this trx: https://he.dtools.dev/tx/920592c5e119703ae2ef48819f4a6b5c49a0daf8 betterdev
was added as an authorized account. The log shows up for poshtoken
but not for betterdev
.
A declarative, efficient, and flexible JavaScript library for building user interfaces.
๐ Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
An Open Source Machine Learning Framework for Everyone
The Web framework for perfectionists with deadlines.
A PHP framework for web artisans
Bring data to life with SVG, Canvas and HTML. ๐๐๐
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
Some thing interesting about web. New door for the world.
A server is a program made to process requests and deliver data to clients.
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
Some thing interesting about visualization, use data art
Some thing interesting about game, make everyone happy.
We are working to build community through open source technology. NB: members must have two-factor auth.
Open source projects and samples from Microsoft.
Google โค๏ธ Open Source for everyone.
Alibaba Open Source for everyone
Data-Driven Documents codes.
China tencent open source team.