Dev? Python?
Knowing a Python dev?
#Bismuth starts some bounty projects, spread the word, more to come!
https://github.com/bismuthfoundation/Awesome-Bismuth/blob/master/Bounties.md
One is Python, the other one is Html/Js
Topic: 🤖[ANN][BIS]Bismuth 2.0 - Beyond DeFi - page 36. (Read 156348 times)
So for these shared masternode services, do you send your bismuth to an address you don't control to 'buy' a part of the masternode, and hope that the owner will provide you the correct payout amount for running that node? And do you also have to wait until all the 'seats' are full before payouts start?
Shared nodes are great but just want to make sure I (and everyone else) understand the possible risks before sending anything through.
Shared nodes are great but just want to make sure I (and everyone else) understand the possible risks before sending anything through.
- Sending the Bis to an address you don't control is a technical requirement. The alternative being running and maintaining a full HN yourself (10K bis).
I think it's the same for any shared masternode out there, be it bis or not.
- Hope that the owner will pay the correct amount: Why reputation is important. For bisafe, all the data is public (you can trace the bis flows, there is the list of all working balances, rewards will also be public, since they are public transactions), nothing is hidden, and it's run by me, also core Bis dev. If you don't trust me, you don't trust Bis. I think pickaxe also has a pretty good reputation in the crypto world.
- With Bisafe, you don't have to wait until all the seats are full to get your rewards. HNs are setup in advance when we see that non working balance within the week raises, so we can plan ahead.
Then on saturday, after the payouts have been issued, we lock the working balances for the next week. We keep some margin so we can "fill up" the potential missing HN collateral with our own funds (that is, we do not put all our bis into HNs so we have "free" bis to fill up yours. We can kinda get not all possible rewards so you can get yours).
I know that on crypto, you are guilty until proven innocent. But unless you have 10K bis and can run and maintain a HN yourself, this offers are a great way to go the easy way.
Some people even sent 20K, 30K and even more in the service, so they could run a HN themselve, but prefer not to bother with setup, hosting and maintenance.
It's a choice, and a matter of trust.
https://twitter.com/EggPoolNet/status/1036629486874312706
#Bismuth Hypernodes freshly launched.
More than 2M Collateral already.
And guess what? 2 shared Hypernodes services are now available.
https://hyper.bisafe.net , 1K $BIS seats, powered by Eggdrasyl and Iyomisc
https://pickaxe.mn/product/bis/ , 250 $BIS seats, powered by pickaxe.
#Bismuth Hypernodes freshly launched.
More than 2M Collateral already.
And guess what? 2 shared Hypernodes services are now available.
https://hyper.bisafe.net , 1K $BIS seats, powered by Eggdrasyl and Iyomisc
https://pickaxe.mn/product/bis/ , 250 $BIS seats, powered by pickaxe.
So for these shared masternode services, do you send your bismuth to an address you don't control to 'buy' a part of the masternode, and hope that the owner will provide you the correct payout amount for running that node? And do you also have to wait until all the 'seats' are full before payouts start?
Shared nodes are great but just want to make sure I (and everyone else) understand the possible risks before sending anything through.
Number of Bismuth Hypernodes per round are now plotted at bottom of https://hypernodes.bismuth.live/?page_id=21
Pretty smooth launch!
< 10 hns: was internal testing
up to 40/45: pre-release, then release.
Pretty smooth launch!
< 10 hns: was internal testing
up to 40/45: pre-release, then release.
I want to ask how the shared hypernode works, I didn't find to much info on the website or onto this thread. Do we need to send our coins to a pool like a POS pool - I don't want to mention any here - or sign a message from the wallet containing the coins? Thank you in advance, K!
Real thread is on the official Bismuth discord, #hyper-bisafe-net channel but I can give some info here.
There are now 2 shared HN services.
You have to send your coins in any case, since to be activated a HN has to sign the reg message from a single collateral account.
So, whatever the service, all shared funds have to be consolidated onto a single wallet per HN.
I personally run the bisafe.net service. Funds are splits into distinct 30K wallets, one per HN, cold stored after registration.
iyomisc, operator of dragginator.com, is my backup in case I have an accident so the funds are not lost.
You can claim the funds back when you want - no large lock in period - just some notice so we can plan ahead. You ask some funds back by signing a message, let 2 saturdays pass and you get them.
There is already something like 335K deposited to the service, some large accounts, should give an idea of the trust of the current users.
Greetings, Is that token will be treated as official currency of the forum to take part into auction or purchase advertisement. I hope this is not joke because it is started by admin of this forum so that I will keep this under my watch list before take any action.
I am very impressive with this project and It seems it's an platform of many integrated blockchains through a modular framework
Generic spam is a pain you know
Yes, the 'merit' system is not enough to stop the spam or generic posts as I saw around bitcointalk. Anyway I want to ask how the shared hypernode works, I didn't find to much info on the website or onto this thread. Do we need to send our coins to a pool like a POS pool - I don't want to mention any here - or sign a message from the wallet containing the coins? Thank you in advance, K!
I am very impressive with this project and It seems it's an platform of many integrated blockchains through a modular framework
Generic spam is a pain you know
I am very impressive with this project and It seems it's an platform of many integrated blockchains through a modular framework
https://twitter.com/EggPoolNet/status/1036629486874312706
#Bismuth Hypernodes freshly launched.
More than 2M Collateral already.
And guess what? 2 shared Hypernodes services are now available.
https://hyper.bisafe.net , 1K $BIS seats, powered by Eggdrasyl and Iyomisc
https://pickaxe.mn/product/bis/ , 250 $BIS seats, powered by pickaxe.
#Bismuth Hypernodes freshly launched.
More than 2M Collateral already.
And guess what? 2 shared Hypernodes services are now available.
https://hyper.bisafe.net , 1K $BIS seats, powered by Eggdrasyl and Iyomisc
https://pickaxe.mn/product/bis/ , 250 $BIS seats, powered by pickaxe.
A few stats about the Bismuth Hypernodes:
https://www.slideshare.net/EggdraSyl/bismuth-hypernodes-stats-revealed
https://www.slideshare.net/EggdraSyl/bismuth-hypernodes-stats-revealed
Hi, Team!
I think your idea is really interesting and nice, I like your idea. I want to ask what distinguishes your plan from another project? And can you name any country that works with your idea?
I think your idea is really interesting and nice, I like your idea. I want to ask what distinguishes your plan from another project? And can you name any country that works with your idea?
If someone can make video step by step tutorial how to make hypernode and post it on youtube it would be very helpful. I will pay him $30.
I would gladly take those $30 but I think there's already a guide on the github if i'm not mistaken, check it out:
https://github.com/bismuthfoundation/Bismuth-FAQ/blob/master/Hypernodes/tmp.md
If you run a node:
- make sure config.txt > quicksync=False
- restart node to reset banlist and catch-up the valid, longest chain
(or you can update to latest release v4.2.6.2)
https://github.com/hclivess/Bismuth/releases
This is a cleanup release after the emergency fix, which includes removal of the quicksync code parts. Full change log is included below:
Code:
- Removed quicksync feature for security considerations
- Extended utilisation of hyperblocks to increase synchronization speed
- Added anchors to coherence checks to greatly reduce node start time
- Increased refresh delay on wallet to prevent it from being stuck when using slower connection
- Added multiple json output functions to commands.py and node
- Added addlistlimmir function to list a given number of mirror blocks of an account
i just want to say that i'm excited for this. i've noticed that the devs always pull through when they announce something. wallet update in a week? BOOM, update in a week.
coin will be on crypto bridge in 2 weeks? BOOM, 2 weeks later the coin was there.
coin will be on crypto bridge in 2 weeks? BOOM, 2 weeks later the coin was there.
If someone can make video step by step tutorial how to make hypernode and post it on youtube it would be very helpful. I will pay him $30.
Bismuth HyperNodes
Install log on an Ubuntu Server 18.04 Machine
https://github.com/bismuthfoundation/Bismuth-FAQ/blob/master/Install/Ubuntu_18.04_Install.md
This project is interesting because its own system governing digital distribution that is currency. as well as the maintenance of the infrastructure automatically. Its different and cool,there will be many users.
Thats right. I just realized that the time will come when all cryptography based coins will be antiquated meaning finance industry will cease to exist as a whole. These markets especially crypto markets are just to make fun, nobody deems them source of income. Hard work at the farm or in the field - like in former times - is orders of magnitude more profitable.
I got a question though (might be to the wrong person). No code is perfect, and we know that there might be attacks on the PoW-chain (seen in a lot of especially new chains over the years). What I don't understand with the whole "2 chains is better than one" is how the PoW-chain will keep tabs on the PoS-chain? Will everything fail if the chains aren't coming to the same conclusion? If I, in some way, manage to get a 51%-attack on the PoW-chain, will I just invalidate the block since PoS-chain isn't coming to the same conclusion?
It's not so simple. There are several mechanisms, and the pos is not a "controler" of the pow chain in the sens where it does not validate or sign pow blocks.
It's more loosely coupled than that, and merely observes to report strange behaviour from the pow actors.
Lots of partial docs are done and will need rework, check the official github, some reading are awaiting already https://github.com/bismuthfoundation/hypernode
Jump to: