A message from our CEO about the future of Stack Overflow and Stack Exchange. Read now.
6

Here's my takeaway, and technical people please feel free to correct me: This blog post is about how every node can pick their own tip selection algorithm, which is the method by which they decide which two transactions to attach a new transaction to (as each time you send a transaction to a node, you confirm two previous ones). As nodes can do whatever ...


6

No, because when you attach an address, a zero-value transaction is done to the address. I.e. it's an incoming transaction to the target address and doesn't reveal the private key.


3

The transaction that is done when "attaching to tangle" doesn't have a sender address. It's just one address—the new address—in that transaction. The action just adds an address connected to your seed to the tangle. It doesn't reveal any part of your key either. If you look at your linked transaction the signature field is actually empty (only 9s) as well as ...


3

Unlike other systems like Bitcoin, IOTA transactions do not distinguish between source and destination addresses. Every transaction in a bundle has exactly one address. If the transaction value is negative, it is considered a spending transaction and the address is considered a source address (and it will need a signature of the bundle hash). If the ...


3

Attaching an address is just sending a 0 value tx to this address. You can use the sendTransfer method of the JavaScript library. It handles the tip-selection (branch- and trunkTransaction) and conversion to trytes for you. import { composeAPI } from '@iota/core' const iota = composeAPI({ provider: 'http://localhost:14265' // replace with your IRI ...


3

You use getTransactionsToApprove to get the two transactions/tips that you need to use in your PoW. Then you must craft your transaction trytes, the Javascript libraries help with this. Then you include the two transactions, your trytes, and few other parameters as input for the cCurl program. This program can be run on the command line (C# program) or via ...


3

It means that the node your wallet is talking to did not return the expected response to your API call. Usually it is a problem with the node and the issue can be fixed by changing to another one. The Bitfinex node has been known to report "I'm depressed, leave me be." during times of heavy network load, which could cause this error.


2

Attaching such old (Curl) addresses might work, but it is by design that it does not most of the time, because usually this is not what you want to do (if you do not want to lose your funds). Read below for more details. Keep in mind: NEVER send any funds to old Curl addresses (generated by tools before the Curl to Kerl update). The iota node has some ...


2

The following Python code can be used to attach an address to the tangle import time from iota import Iota from iota import Address from iota import ProposedTransaction ''' both work, with and without checksum ''' address = 'KO9CVYUHZSZGHCXSRXDHBTT9U9WUJROIBSRNYKUBXOWONSGKIEHBOXBPKVG9FCHFCJ9QZQTRBYTESRQLCEGNFPFEVD' address = '...


2

Yes Pow must have been done... but not locally. To perform the POW locally, you need to setup an iotaClient with a object able to perform the pow locally. You do this in the @Setup for your test with this line of code : iotaClient = new IotaAPI.Builder().localPoW(new PearlDiverLocalPoW()).build(); This will create a client able to perform the pow locally ...


2

It's the responsability of the node owner to configure it's node properly. The recommended setting is to not allow remote-POW (therefore interruptAttachingToTangle is a NOOP). If the node owner allows remote-pow, it is probably a good idea to not allow remote call to interruptAttachingToTangle. (using remote-limit-api parameter)


2

"Inconsistent subtangle" - transaction you want to promote is referencing an invalid transaction (or one that was confirmed in other reattachment). That means you have to use reattach. "Cannot find tail" - not sure, maybe this node doesn't see this transaction or it isn't a tail (transaction with index 0 in the bundle) "Inconsistent tips pair selected" - ...


1

A team working on a spamming tool tried to implement GPU transaction spammer but they ran into big issues with OpenCL as of 20/2/2018. The library is not ready as it always crashes, so it's whether to dig into the OpenCL or wait.


1

IOTA has some OpenCL context Library: https://github.com/iotaledger/clcontext But I don't know what you can do with it. Maybe this is what people ware referring to.


1

Following from the light wallet: https://github.com/iotaledger/wallet/blob/4a50e49c15c76ec57793614eafaa2edf54352927/ui/js/ui.addresses.js#L55 https://github.com/iotaledger/wallet/blob/4a50e49c15c76ec57793614eafaa2edf54352927/ui/js/ui.addresses.js#L77 and the cli-wallet (line 41): https://github.com/iotaledger/cli-app/blob/master/lib/commands/address.js it ...


1

In the Tangle randomness is important, if some portion of nodes are selsifh (try to choose the best two tips) we don't want a situation like Figure 1 from this blog post (here). In other words, only few nodes get lucky, because there will be competition between the "best two tips". In this situation we'll have a thin Tangle and lots of transactions orphaned ...


Only top voted, non community-wiki answers of a minimum length are eligible