Pages:
Author

Topic: Obyte: Totally new consensus algorithm + private untraceable payments - page 80. (Read 1234271 times)

newbie
Activity: 36
Merit: 0
member
Activity: 762
Merit: 35
Thanks for the info.

I think this should be explained when you get the question in the wallet.
Imagine mine (and probably everyone else's) suprise and head scratching
when they ask you if you trust one or another byteball address Smiley


Now i have more questions: can i run a hub under windows OS?
I saw the github repository, but unfortunately have minimal Linux experience.
If it is Linux only, what are the system requireents and is there
a (very) detailed guide how to set it up?

I get why you ask about running the Hub, but you really shouldn't be running a Hub if you are not building your own wallet for Byteball because asking existing Byteball users to switch to your Hub is not something you want to do (you are not going to get many people to do that). And if you decide to quit running the Hub, it currently breaks the experience of all the people who added you as the Hub.

Please explain why adding a new node (hub) is bad.
As far as Iunderstand it makes the netork faster and more decentralized.

Yes, it is not bad, it is essentially same as relay, but has features that you do not need (relaying e2ee chat messages). It is more needed for wallet developers, who also need to send push notifications to their app. It is only bad for users if they start to use your Hub address and then you quit running Hub.

Relay is simpler version of Hub and makes the network faster and more decentralized too.
If you want to build an exchange or other business that sends or receives payments then you need to install headless-wallet, which can also act as relay.

Thanks for the info! I'll be waiting for a detailed guide on running a relay then Smiley
newbie
Activity: 28
Merit: 0
On-chain oracles can post data (such as timestamps, exchange rates, weather, various events) directly to the database, then that data can be referenced from spending conditions
full member
Activity: 770
Merit: 100
new witnesses=  Grin
Rogier Eijkelhof  thanks
full member
Activity: 563
Merit: 103
Thanks for the info.

I think this should be explained when you get the question in the wallet.
Imagine mine (and probably everyone else's) suprise and head scratching
when they ask you if you trust one or another byteball address Smiley


Now i have more questions: can i run a hub under windows OS?
I saw the github repository, but unfortunately have minimal Linux experience.
If it is Linux only, what are the system requireents and is there
a (very) detailed guide how to set it up?

I get why you ask about running the Hub, but you really shouldn't be running a Hub if you are not building your own wallet for Byteball because asking existing Byteball users to switch to your Hub is not something you want to do (you are not going to get many people to do that). And if you decide to quit running the Hub, it currently breaks the experience of all the people who added you as the Hub.

Please explain why adding a new node (hub) is bad.
As far as Iunderstand it makes the netork faster and more decentralized.

Yes, it is not bad, it is essentially same as relay, but has features that you do not need (relaying e2ee chat messages). It is more needed for wallet developers, who also need to send push notifications to their app. It is only bad for users if they start to use your Hub address and then you quit running Hub.

Relay is simpler version of Hub and makes the network faster and more decentralized too.
If you want to build an exchange or other business that sends or receives payments then you need to install headless-wallet, which can also act as relay.
jr. member
Activity: 111
Merit: 2
Please explain why adding a new node (hub) is bad.
As far as Iunderstand it makes the netork faster and more decentralized.
It is not bad. For using yours, users will have to change the hub config in their wallets. You could customize bot store (it is a list which is downloaded from hub).

AFAIK a hub is full node + service for light wallets
a full node by itself doesn't serve light wallets
member
Activity: 762
Merit: 35
Thanks for the info.

I think this should be explained when you get the question in the wallet.
Imagine mine (and probably everyone else's) suprise and head scratching
when they ask you if you trust one or another byteball address Smiley


Now i have more questions: can i run a hub under windows OS?
I saw the github repository, but unfortunately have minimal Linux experience.
If it is Linux only, what are the system requireents and is there
a (very) detailed guide how to set it up?

I get why you ask about running the Hub, but you really shouldn't be running a Hub if you are not building your own wallet for Byteball because asking existing Byteball users to switch to your Hub is not something you want to do (you are not going to get many people to do that). And if you decide to quit running the Hub, it currently breaks the experience of all the people who added you as the Hub.

Please explain why adding a new node (hub) is bad.
As far as Iunderstand it makes the netork faster and more decentralized.
full member
Activity: 563
Merit: 103
Thanks for the info.

I think this should be explained when you get the question in the wallet.
Imagine mine (and probably everyone else's) suprise and head scratching
when they ask you if you trust one or another byteball address Smiley


Now i have more questions: can i run a hub under windows OS?
I saw the github repository, but unfortunately have minimal Linux experience.
If it is Linux only, what are the system requireents and is there
a (very) detailed guide how to set it up?

Yeah, it works on Linux, Mac and Windows because NodeJS works on all of them. Maybe it can be more difficult on some machines because they might have different stuff pre-installed. I think the biggest obstacle might be sqlite module, which needs Python or MS build tools, but that can be resolved by copying missing folders from your wallet installation.

I get why you ask about running the Hub, but you really shouldn't be running a Hub if you are not building your own wallet for Byteball because asking existing Byteball users to switch to your Hub is not something you want to do (you are not going to get many people to do that). And if you decide to quit running the Hub, it currently breaks the experience of all the people who added you as the Hub.

If you want to help Byteball network then you should be running a relay, which advertises its address itself to other nodes, but doesn't have options to suggest replacing the witnesses.
https://github.com/byteball/byteball-relay

(Very) detailed guide how to setup NodeJS and a headless-wallet/hub/relay are coming soon. Currently all tutorials expect that you already have NodeJS and other essentials installed.
member
Activity: 762
Merit: 35
Thanks for the info.

I think this should be explained when you get the question in the wallet.
Imagine mine (and probably everyone else's) suprise and head scratching
when they ask you if you trust one or another byteball address Smiley


Now i have more questions: can i run a hub under windows OS?
I saw the github repository, but unfortunately have minimal Linux experience.
If it is Linux only, what are the system requireents and is there
a (very) detailed guide how to set it up?
full member
Activity: 563
Merit: 103

1. why I should prefer one addres before another?

for me they are just a bunch of numbers and letters

At least you have to agree on 11 of 12 network witnesses in order to use the platform.

2. what happens if a trusted witnes goes rouge?

3. What happens when he dies?
Nothing, if their node is still running.

How do I know if i should trust

JEDxxxxxxxxxxxxxxxxxxxxxxxx

or

4GDxxxxxxxxxxxxxxxxxxxxxxx ?



Your passport number is also just bunch of letters and numbers, the pledge PDF says that Rogier is behind that address.

You might want to read the pledge PDF again https://medium.com/byteball/first-decentralized-witness-candidate-rogier-eijkelhof-9e5619166334

Quote
I have set up a “dead man’s switch” failsafe construction to make sure if I come to die or otherwise unable to personally operate or maintain my witness node, the information to unlock my node keys will become available to 3 trusted members from the community, secured with 2-out-of-3 keys encryption.

All the other witnesses are in control of the Tony, so if you want Byteball to become more decentralized, you will replace Tony's witness. Also, default Hub is in control of Tony, so basically the founder of Byteball suggest you to replace witness that is not him anymore. When all 11 witnesses have replaced (Tony have said to be only one) then it becomes a matter if I should trust old one or new one, until then replace it makes Byteball more decentralized and should be no-brainer thing to do.
member
Activity: 762
Merit: 35

1. why I should prefer one addres before another?

for me they are just a bunch of numbers and letters

At least you have to agree on 11 of 12 network witnesses in order to use the platform.

2. what happens if a trusted witnes goes rouge?

3. What happens when he dies?
Nothing, if their node is still running.

How do I know if i should trust

JEDxxxxxxxxxxxxxxxxxxxxxxxx

or

4GDxxxxxxxxxxxxxxxxxxxxxxx ?

jr. member
Activity: 111
Merit: 2

1. why I should prefer one addres before another?

for me they are just a bunch of numbers and letters

At least you have to agree on 11 of 12 network witnesses in order to use the platform.

2. what happens if a trusted witnes goes rouge?

3. What happens when he dies?
Nothing, if their node is still running.
member
Activity: 762
Merit: 35
member
Activity: 762
Merit: 35
I just got message from the wallet:

NEW WITNESSES

The hub suggests replacing the following witnesses:

JEDxxxxxxxxxxxxxxxxxxxxxxxx

to

4GDxxxxxxxxxxxxxxxxxxxxxxx

REPLACE               Maybe LATER

Can someone explain what this means?

Who are these witnesses? Whom should i trust and why?
tyz
legendary
Activity: 3360
Merit: 1533
what i found is this:

i was not able to start the osx wallet and received this message.

Uncaught exception: Error: message encrypted to unknown key, device , len=228. The error might be caused by restoring from an old backup or using the same keys on another device.

i had this problem after I had done this:

I changed the hub from https://byteball.fr to byteball.org/bb

so I had old messages encrypted with my old key and stored on the other hub.

what solved the problem was:
i switched back the hub.
i deleted all the messages.
then i changed the hub and received the error message.
the wallet crashed.
the after the next restart the wallet worked again.

I need help with an error message that appears on client launch from one day to another. New installation of the client software did not solve the error. I use MacOs.

Message encrypted to unknown key. The error might be caused by restoring from an old backup or using the same keys on another device



Is anyone here who can help me on this? Someone pm'ed me and told me the issue arise if one run the same wallet on different machines. However, I have run the wallet only on one machine since I am dealing with Byteball. I also did not restore a wallet backup or something else. Just want to get back access to my Bytes :/

I remember a similar error was reported on our Slack helpdesk. AFAIR it could be resolved by starting the wallet several times.

Thank you both for your help! I followed both suggestions and after several restarts I got a message at startup "whether the hub X should be replaced by hub Y?" I clicked on "replace" button and now my wallet works again. I have no idea which of the two methods led to success.
newbie
Activity: 36
Merit: 0
legendary
Activity: 2044
Merit: 1055
I need help with an error message that appears on client launch from one day to another. New installation of the client software did not solve the error. I use MacOs.

Message encrypted to unknown key. The error might be caused by restoring from an old backup or using the same keys on another device



Is anyone here who can help me on this? Someone pm'ed me and told me the issue arise if one run the same wallet on different machines. However, I have run the wallet only on one machine since I am dealing with Byteball. I also did not restore a wallet backup or something else. Just want to get back access to my Bytes :/

I remember a similar error was reported on our Slack helpdesk. AFAIR it could be resolved by starting the wallet several times.
newbie
Activity: 36
Merit: 0
You're Machiavellian Tarmo888 😂😂😂 We are all Agent Smith.
Pages:
Jump to: