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

Working now. Thank you.

Coleslaw

We sometimes we get waves of spam, maybe yours got accidentally banned with others. What's your name on Discord?

Using that invite link gives me a message saying that I have been banned. No idea why.

I meant, there is a limit of how many inputs (MAX_INPUTS_PER_PAYMENT_MESSAGE) and outputs (MAX_OUTPUTS_PER_PAYMENT_MESSAGE) can be in one transaction. I double checked that it's 128, so if you have rewards set each day for year then all of these unspent outputs doesn't fit into a new transaction. But that should give different error message too, which is odd.

I would try to sent half of the amount to other wallet (you can create multiple wallets within app), if that didn't work, half of that. If it did work, then try full amount again. You could try to send to same wallet too, but I am not sure if that will fix the problem.

Can you join Obyte Discord server and ask further support from #helpdesk channel? https://obyte.org/discord

Thank you for the quick reply. I am not talking about WCG points. I'm talking about the actual bytes. The only transactions to the wallet are the somewhat daily rewards for my WCG contributions. So, there shouldn't be much in the ways of transactions. My order providers is set to automatic update in the wallet and the wallet is always open. And to be clear, I just have the one wallet address.

When you say there is a limit on unspent outputs, what exactly does that mean? As I mentioned above, the only transactions are when I receive the WCG payments and is at most once a day if not every couple of days. Sometimes it takes up to 4 days to get the award.

Are you talking about the bytes or WCGpoints? Because WCGpoints are not transferable, they are like gratitude tokens, which other bots can use to determine your status or discount.

You should be able to send out all the bytes in your wallet, just make sure your Order Providers (Witness) list is up to date because if it can't find a suitable parent for your transaction then it can't spend these funds either, but that usually gives different error.
There is also a limit of unspent outputs it can use at once (120), so maybe you have so many incoming payments that it can't send out all at once, try to consolidate smaller batches into different wallet and then send all from there.

This has probably been mentioned several times in the past, but I am not finding good and organized information that covers it clearly. When I try to send a payment in the wallet, I keep getting the message that I don't have enough spendable funds. My wallet consists of the rewards from running WCG. When I look in my history transactions, they all state that they are confirmed in the finality. How can I check in the wallet what my actual spendable amount is exactly? I did try transferring a much smaller amount and it went through. However, trying to send the bulk of it gives me the error. I'm sure if I clicked send all minus fees it would work, but a friend of mine saw that it didn't send all of his balance in one transaction.So, I'm assuming there is still something not fully spendable that isn't blatantly clear in the wallet. Can someone shine some light on how the wallet behaves and how to find your actual spendable amount?

Obyte is tyrannic government resistant, which means that unless all governments suddenly agree on something, there is no danger. The breaking point is actually 6-7 Order Providers, not 12 because if you take 6 out then there is no longer majority. If they take out 7 then they have the majority.
Getting all the governments suddenly co-operate with each other and agree on something like that is quite far fetched, especially when there is nothing illegal in what the full nodes are doing. Today, we no longer have majority of Order Proviers in one jurisdiction, so Obyte doesn't have a single-point failure https://stats.obyte.org/witnesses.php

If 6 governments indeed get simultaneously agents to knock on doors of 6 Order Providers then which judges are going to sign that? These 6 people should all have to be breaking some law for the agents to break in. So, Obyte is not in danger if one of the governments loses it's mind or one of the Order Providers is accused in something criminal. Running a full node is not criminal, posting transactions on cryptocurrency platform is not criminal either. Order Providers don't decide whose transaction is valid or not, the whole network does. Bitcoin is protected against same thing - multiple governments going mad, but Bitcoin miners actually decide whose transactions get confirmed, Obyte Order Providers doesn't. https://medium.com/obyte/from-blockchain-to-dag-getting-rid-of-middlemen-28afa7563545

In terms of what will happen if government seizes the machines, if it's even located in the same place as the Order Provider himself - the worst thing they can do is shut the machines down because if there is no majority of Order Providers posting anymore, no new transactions will get stable (confirmed). People could still post new transactions, but the part of the DAG with unstable transactions will not become stable. They could also modify the code and post transactions out of order, but that would just signal everyone that Order Provider is acting bad. They can't change the history, that's blockchain feature, not Obyte's.

If they somehow would get hands on majority of Order Providers (7) and make those post transactions out of order then that would just break the whole network and the community would need to hard-fork.

There is more about exact this thing on Obyte blog https://medium.com/obyte/dag-vs-blockchain-6d2d99f10bd9

I've been a fan of Obyte for over 3 years now, and it surely is one of the most interesting projects out there.
However, I still have doubts about its resilience. It should be government-resistant.
What would happen if a government would sent 12 agents to take care of the 12 Order Providers simulaneously? Could it bring down the network and maybe rewrite the history of the DAG?
I hope not, but I'd need to hear a convincing answer on why not. It's a question that deserves an answer.

DECENTRALIZATION is here! Obyte is the first DAG to become fully DECENTRALIZED!

The 7th Poll has ended and the chosen new Order Provider is the Institute For the Future (IFF) of the University of Nicosia.

Now 7 out of 12 Order Provider nodes are independent.

Thank you Rogier Eijkelhof, Fabien Marino, Bosch Connectory Stuttgart, PolloPollo, Bind Creative, Cryptoshare,  University of Nicosia, and everyone who voted in order provider polls for getting us here!

https://medium.com/obyte/obyte-achieves-full-decentralization-by-adding-university-of-nicosia-as-an-independent-order-baaef0505392

Isn't the idea of digitally signing something that it also verifies that the file is a whole and not modified some way? Only thing that isn't digitally signed is the AppImage for Linux, which has a hash written down on release notes. All the digitally signed ones should warn you automatically if the file is corrupted or modified, so what good will an extra hash do? What's the point of additional hashes if verifying the executables is already built-into the OS.

Also, if you get tricked into downloading from fake Github, what would stop the fake Github from having fake hashes too? What you should look for instead is that the installer is signed by verified publisher: Byteball Foundation

We sent some THANKs, to support with our 'No' Money your work. Many THANKs for your concept, your well done development, and for your support also!

https://www.facebook.com/vortexledger/photos/a.606340069783514/995379484212902/?type=3&theater

Good morning gentlemen. I am Steve Safronoff, Partner and COO and Head of Business Development and Strategy/Plan Expert at Byteball. I have been on the team for 3 years, today I felt like it was finally time to see what is happening in the trenches. Byteball is running out of money but this to me means bigger opportunity. That is all for now, gentlemen. Onwards

Wallet update:
Version 3.2.0 released.
This is a mandatory upgrade that fixes a bug in transaction size calculation that could allow sending data for free.

Both full and light nodes need to upgrade.
All headless nodes need to npm update to update to the latest core version and restart.
The updated version is scheduled to be activated at MCI 5530000 which is expected around July 18. This is the deadline for the upgrade.

Also in this release:
- improved translations
- added human readable display of some smart contract clauses used by PolloPollo

https://github.com/byteball/obyte-gui-wallet/releases

Thanks to "Made On Obyte" and Obyte, PolloPollo is first to test crowdfunding a bounty to further leverage the power of our P2P charitable model.

Juicy rewards up for backers as well ❤️

https://madeonobyte.org/funding/pollopollo-feedback-module-14qaq3qqzze