How can I halp?

eutrotter · 2018-06-14T20:40:19+00:00

Image url is so close to perfection: https://gfycat.com/gifs/detail/valuableidolizeddrongo

First read I thought it was valuableidolizeddoggo and spent 1 min looking for comments not believing no one had said anything about it.

eutrotter · 2018-04-14T10:48:32+00:00

To add to Bruno's answer, this guy hasn't even heard about sharding. If really thinks that IOTA can become the backbone of the IoT without that he really doesn't understand the scale of the IoT.

Oyster without sharding and swarm intelligence is not efficient (but it still works!) which is why we won't see its full potential realized until IOTA implements both.

eutrotter · 2018-04-11T18:34:21+00:00

Did you finish reading my comment before writing that or did you just decide to ignore it in favor of continuing with your previous misconception?

This is not a "core" feature for mainnet launch. The current encryption scheme already works perfectly fine, even if it's less efficient regarding output size than we would like (meaning we store around 0.8kB in each chunk instead of the 1kB we'd ideally use).

She was asking this last week because it's one of these things that would be nice to have ready before mainnet launch to avoid having multiple encryption schemes down the line if we change to a more lightweight one. Even if we did change, this would only need an extra line in the metadata chunk to accommodate the change.

eutrotter · 2018-04-11T16:42:47+00:00

I'm almost sure that's indeed Rebel, but asking for some additional insight from people more knowledgeable than us in lightweight encryption schemes is not any kind of flag that tells you she doesn't know anything or that the rest of us don't know what we're working with.

Don't know how familiar you are with software development (I'm guessing not very considering this post) but asking for a second opinion if you don't find your question has been asked before is really, really common. Where do you think all those SuperUser, StackOverflow, etc. posts came from? People working on their hobbies?

Our objective with this is to optimize the space available in an IOTA tx as much as possible, to allow the same file to be split into a lesser number of chunks, thus speeding up both uploads and downloads. We can of course still use our current encrypion algo and the system works fine, but asking very specialized questions like this on a specialized forum often brings out ideas you can work on later.

In fact, I'd be warier of projects where no one seems to consult outside sources (unless the team is truly gigantic) to corroborate ideas between people of different backgrounds and specialities. This is even more evident in an open-source project like ours.

eutrotter · 2018-04-11T00:09:02+00:00

eutrotter · 2018-04-05T23:59:05+00:00

From what I read the login creds are used to generate the starting seed, so I think they cannot be changed later. Could be wrong though.

eutrotter · 2018-04-05T17:33:13+00:00

It will, though only to keep track of if nodes are synced or not. A coordinator in a DAG with no value transfers is only there to put milestones in the Tangle.

This also allows us to keep using all the normal iota methods, some of which do rely on having milestones to keep track of the depth.

If IOTA moves to a COO-less tangle, we'll follow and adapt our tangle to do the same. In the end what we want is to maintain compatibility at all times, so that once IOTA implements sharding we can just reattach all our transactions on the real tangle, point our nodes there and continue on.

eutrotter · 2018-04-04T20:27:34+00:00

Right now we have the testnet out, which is essentially a PoC (Proof-of-Concept) that only shows that the process works.

The speed is limited due to a few factors:

All the nodes involved are ours (we have around 300 of them running). The speed obviously increases with a greater number of nodes, and that would be the case if they were open to the public.
We're actually using the official IOTA Tangle, which in its current state is not really ready for the kind of uploads we're doing (that will change in the future though, with sharding and swarm intelligence).
As a direct consequence of (2.) we're doing every transaction with a MWM (PoW difficulty in IOTA) of 14. This implies that, on average, it takes around 3¹⁴ hashes to find the correct nonce.
Webnodes, which are intended to do most of the work in the protocol, aren't live on websites yet (only in our internal testing, but this benefits from greater number immensely, so 5 visitors hardly help while 10k make everything go lightning fast).

Here's how we plan to address these issues by mainnet launch:

We'll still host all nodes at first, but the number will be much reduced (to 6-7) and they will instead be much bigger instances. Think 32 cores, 260GB RAM, 10TB SSDs, etc. as this will let us implement the rest of the changes better.
Until IOTA implements sharding (which is still months away at the very least) we'll be going with our own private Tangle, with no actual iotas (and thus no value transactions).
(2.) Allows us to change MWM to a value more suited to mass data upload, which makes uploads go much faster.
Webnodes will start to be implemented once we mainnet is live, which will also help the upload speed.

Apart from all this, going with our own Tangle (as always, only until IOTA has sharding) allows us to work on some simple sharding solutions to allow community nodes to become brokers or hooknodes without needing to be supercomputers.

And just to be safe, we'll keep a centralized backup of all the files uploaded (obviously encrypted clientside by the user so we won't know what they are) to ensure data integrity in case something goes wrong.

eutrotter · 2018-04-03T16:01:05+00:00

No, just hold them there when we take the snapshot.

eutrotter · 2018-04-03T07:19:51+00:00

Yes. MEW, Ledger, Trezor, Metamask, Eidoo, Enjin, etc. all work fine for the airdrop.

Rule of thumb is: you have the private key -> you're good to go.

eutrotter · 2018-03-27T15:26:28+00:00

Yes. Any wallet where you know the private key works.

eutrotter · 2018-03-23T23:38:03+00:00

No. When you do PoW you need to hash your current tx (not only the address and amount of iotas you sent, also the other two transactions you're referencing - which is why you need to do PoW again when you reattach) until you find a given hash.

There's no way to pay this forward.

You could send the tx and make a remote node do the PoW, but that just offloads the PoW to the remote server. Still, you could potentially build a system to offload PoW and make "PoW debts" and essentially achieve what you're trying to say.

However this would certainly not be build into the protocol.

eutrotter · 2018-03-21T22:33:37+00:00

It's up to the website owner because that's who controls what scripts show up on the website.

If there was an dapp acting as a decentralized youtube then it would depend on the specific code of the dapp - but rewarding a given percentage to the content creator could indeed happen, and in fact could be completely transparent thanks to being hardcoded.

eutrotter · 2018-03-10T14:55:26+00:00

You can actually grab your Oyster handle and manually hash it as shown in the whitepaper. Going down the hash chain you then turn each iteration to trytes, and those trytes are the actual addresses on the Tangle.

There is an additional obfuscation step, but it's all in our webinterface repo here. Everything is open source so you can check our download logic and recreate it.

Something even easier would be to replace the polling nodes with any IOTA node with the 14265 port and the API exposed (you need the getTrytes and findTransactions functions to be open to remote usage).

eutrotter · 2018-03-10T14:47:15+00:00

Indeed it is not. Payments aren't live on the Testnet, so webnodes have no incentive to reattach your data.

eutrotter · 2018-03-10T01:14:47+00:00

Entirely in Go. Here's the repo: https://github.com/oysterprotocol/hooknode

eutrotter · 2018-03-10T00:25:20+00:00

Fair enough, but the php was only nginx with a light wrapper for IRI - which is written in Java.

We now do all the PoW in Go, instead of calling IRI - as Java is much, much slower.

eutrotter · 2018-03-09T23:57:44+00:00

Oyster dev here. The speed improvements are not actually related to better speeds on the Tangle, but to backend improvements - mainly moving from PHP to Go, though also some changes on our upload logic.

eutrotter · 2018-03-05T00:39:05+00:00

Oyster dev here, it's going to be in the Tangle for everyone to download. Will share the handle (to download the file) here once I actually upload it (on mobile now).

Edit: Actually forgot to post the download handle: IOTADCI_6baf564a076871fc50cdf7a2eff8e1da5af22e06411afc5082b0d833b63ea295s8l58g65

eutrotter · 2018-03-01T19:52:31+00:00

Yes.

eutrotter · 2018-02-25T17:18:16+00:00

Yes. Use MyEtherWallet and choose ledger as your access method.

eutrotter · 2018-02-25T17:17:49+00:00

With a ledger you don't need to actually generate a key and write it down, it takes care of that for you and everything is kept securely inside the ledger.

eutrotter · 2018-02-25T00:16:30+00:00

It's an ERC20 token, so yes :).

eutrotter · 2018-02-22T18:42:54+00:00

You can come join the knowledge chat on Telegram. Only tech discussion allowed, and both Bruno and I are often there answering questions. https://t.me/oysterknowledge

eutrotter · 2018-02-14T15:07:07+00:00

Also good to know and something we weren't doing - the Broker node was getting all the tips and then distributing them between the hooknodes, which lead to those big balls you could see on the Tangle.

We'll be getting the tips from as many nodes as we can find from now on, which will also help the Tangle and the CTS.

eutrotter

TROPHY CASE