I cannot find a better adjective to describe how great your videos are. Fantastic job! Meanwhile I see a mix use of the term "transaction". For example, in page 3, this quote "Each transaction consists of a bundle of transactions" cause the confusion. The former "transaction" points to the bundle, the green box in page 4, the square in Tangle, while the latter "transaction" is more a part or a sub component inside the former "transaction". I think a better word for the "latter transaction" may be items or entries, or anything. No idea if they are the formal use of transactions in IOTA document (not yet read through). Thanks again.
Aha, you noticed! That was also my problem when making this video. In IOTA documentation, there is no special word to name transactions inside a bundle. They ARE transactions, but entries might be a good alternative. And if you look at the Tangle image a square is called a "transaction" (in IOTA documentation) but in fact it is a BUNDLE of transactions. In the future, for simplicity sake, I will be using the word "transaction" instead of "a bundle of transactions".
How do i create automated transaction from 1 transaction to 2 deifferent wallets. One of the wallets takes some % (lets say 5%) from value of the transaction and displays confirmation of transaction on website. Other wallet takes the rest. What would be the best way to do it? Do i need smart contracts or something?
Hi. Thank you for your video. In Transaction Example 2 (8:44), is it still safe to send 3 IOTAs to Alice's address 2 instead of address 3? I know it's best practice to send IOTAs to an unattached address (Alice's address 3 in this case), but in Transaction Example 3 when Alice sends 3 IOTAs to Bob, she needs to do PoW 6 times. With the 3 IOTAs sent to her address 2 instead, the number of times PoW is done would be only 4. What risk would be incurred then?
Since address 2 has never been used for outgoing tx before (because if it had, it wouldn't have had any funds), how is the prospective 'future' outgoing tx from it going to be an address reuse?
Nguyen, sorry I have made a mistake. Ignore my previous answer. 1) Question: "In Transaction Example 2 (8:44), is it still safe to send 3 IOTAs to Alice's address 2 instead of address 3" Answer: Yes 2) I do not understand the second question. The part "..With the 3 IOTAs sent to her address 2 instead, the number of times PoW is done would be only 4.." is confusing.
Hi. Thank you for the answer. The second part of my question was actually just elaboration on the first. What I meant is maybe it would be less expensive computationally for the 3 IOTAs in Example 3 to be transacted had the 3 IOTAs in Example 2 been sent to Alice's address 2 instead of address 3. You backing the point I raised have satisfied me. A change in the wallet implementation owing to that would be a good idea maybe?
Ah, I now understand your question. You can create a stateful wallet which can store any relevant information to avoid address re-use. Of course you can make this wallet "smart" to make it less expensive computationally by choosing specific addresses which fulfill the transaction.
How many times the "system" checks the adresses looking for founds? After many transaction you'll have found in addreses with hugh indexnumber. When to stop?
Dear Professor, My question is: Can I traceback or find any transaction in the tangle? for example, based on some transaction ID value or any other parameter?
Is there a particular (programming) reason for the construct of the last tx N in the bundle @0:35: branchtx->tip1 and trunktx->tip0. Why not the other way around? Love your vids!
Hi, i think that have a tiny mistake, exactly in 15:52 minute you have with branchTransaction, you said that if it is not the head transaction, it will be hold to tip 0 but i think that you want to refer to tail transaction which won't be holded to tip 0. Thanks for spent your time with us, that was very useful.
My observation is that what you said is matching the video and the slide. However it seems on the branchTransaction, the last condition should be "If this transaction is the *head* transaction" instead of "tail transaction". Only the head transaction is different from others (see the diagram in pg 4) Again, great videos as usual. Great job!
If you use the api call: github.com/iotaledger/iota.lib.js#getaccountdata you can get the latest confirmed balance (= balance of ALL addresses together)
Thanks for the rapid reply. :) If wallet has 3 address address 0 : 1 address 1 : 1 address 2 : 1 In this case, can I send 3 IOTAs by 1 transaction ? Thank you again! :)
Yes. If you use iota.api.sendTransfer it is automatically done. You only need to specify the receive address and the amount. The api automatically starts with address 0...N until the required amount is found. In your example it will use address 0, 1 and 2.
How're the private key and the signatueMessageFragment connected? Please explain us what a theft is doing when he found a double-use address. Thanks for your videos, you're great
I don't understand why there are transactions which are referenced by more than 1 transaction when a NEW transaction only references tips (non-referenced transactions). Can anyone explain this to me?
Let's assume: - The Tangle has a transactionZ (tip) with no transactions referencing it. - Node A receives a transactionA - Node B receives a transactionB The nodes find tips using the Monte Carlo Random Walk algorithm. Lets assume Node A and B find the same tip (=transactionZ) at exactly the SAME time. Now transactionA is referencing transactionZ and transactionB is referencing transactionZ. In this example transactionZ is referenced by 2 transactions. But it is possible it can be referenced by more transactions (3, 4,...)
th-cam.com/video/M9dwwgtbbOU/w-d-xo.html - what is you have 10 addresses and 0 in the first 9, does this mean it always goes through all of them before reaching address 10, where there might be some funds, so that the transaction is successful? Am I missing something? Isn't this slowing down the transaction time?
You are correct! This is how the IOTA Light wallet (desktop) works. This wallet is stateless which means it does NOT store any information. All information is retrieved from the tangle. That is why it take times to display balance information. The current Trinity wallet (mobile) is NOT stateless, it stores information. I assume (not know for sure because the code is not public) all used addresses are stored.
I cannot find a better adjective to describe how great your videos are. Fantastic job!
Meanwhile I see a mix use of the term "transaction". For example, in page 3, this quote "Each transaction consists of a bundle of transactions" cause the confusion. The former "transaction" points to the bundle, the green box in page 4, the square in Tangle, while the latter "transaction" is more a part or a sub component inside the former "transaction". I think a better word for the "latter transaction" may be items or entries, or anything. No idea if they are the formal use of transactions in IOTA document (not yet read through).
Thanks again.
Aha, you noticed! That was also my problem when making this video.
In IOTA documentation, there is no special word to name transactions inside a bundle. They ARE transactions, but entries might be a good alternative.
And if you look at the Tangle image a square is called a "transaction" (in IOTA documentation) but in fact it is a BUNDLE of transactions.
In the future, for simplicity sake, I will be using the word "transaction" instead of "a bundle of transactions".
How do i create automated transaction from 1 transaction to 2 deifferent wallets. One of the wallets takes some % (lets say 5%) from value of the transaction and displays confirmation of transaction on website. Other wallet takes the rest. What would be the best way to do it? Do i need smart contracts or something?
Hi. Thank you for your video. In Transaction Example 2 (8:44), is it still safe to send 3 IOTAs to Alice's address 2 instead of address 3? I know it's best practice to send IOTAs to an unattached address (Alice's address 3 in this case), but in Transaction Example 3 when Alice sends 3 IOTAs to Bob, she needs to do PoW 6 times. With the 3 IOTAs sent to her address 2 instead, the number of times PoW is done would be only 4. What risk would be incurred then?
You are risking your IOTAs to be 'stolen' (because of address reuse for 'future' outgoing tx) vs some 'faster' pow.
Since address 2 has never been used for outgoing tx before (because if it had, it wouldn't have had any funds), how is the prospective 'future' outgoing tx from it going to be an address reuse?
Nguyen, sorry I have made a mistake. Ignore my previous answer.
1) Question: "In Transaction Example 2 (8:44), is it still safe to send 3 IOTAs to Alice's address 2 instead of address 3"
Answer: Yes
2) I do not understand the second question. The part "..With the 3 IOTAs sent to her address 2 instead, the number of times PoW is done would be only 4.." is confusing.
Hi. Thank you for the answer. The second part of my question was actually just elaboration on the first. What I meant is maybe it would be less expensive computationally for the 3 IOTAs in Example 3 to be transacted had the 3 IOTAs in Example 2 been sent to Alice's address 2 instead of address 3. You backing the point I raised have satisfied me. A change in the wallet implementation owing to that would be a good idea maybe?
Ah, I now understand your question. You can create a stateful wallet which can store any relevant information to avoid address re-use. Of course you can make this wallet "smart" to make it less expensive computationally by choosing specific addresses which fulfill the transaction.
Really good explanation! Thank you very much! It helps me much to handle the iota libraries
How many times the "system" checks the adresses looking for founds?
After many transaction you'll have found in addreses with hugh indexnumber. When to stop?
Dear Professor, My question is: Can I traceback or find any transaction in the tangle? for example, based on some transaction ID value or any other parameter?
Is there a particular (programming) reason for the construct of the last tx N in the bundle @0:35: branchtx->tip1 and trunktx->tip0. Why not the other way around? Love your vids!
branch tx must refer to tip (does NOT matter which one)
tip tx must refer to the other tip
but is there any reason why the branch references do not all point to the same tip?
Sorry, I do not know the answer.
You can try: iota.org/IOTA_Whitepaper.pdf
Or iota.stackexchange.com/
Wow, this reminds me of school. Like, I really need to learn this but gosh its a lot to take in sometimes. :) Well done as usual, Mobilefish.
Hi, i think that have a tiny mistake, exactly in 15:52 minute you have with branchTransaction, you said that if it is not the head transaction, it will be hold to tip 0 but i think that you want to refer to tail transaction which won't be holded to tip 0. Thanks for spent your time with us, that was very useful.
I have rewatched my video, but it is correct what a said in the video.
My observation is that what you said is matching the video and the slide. However it seems on the branchTransaction, the last condition should be "If this transaction is the *head* transaction" instead of "tail transaction". Only the head transaction is different from others (see the diagram in pg 4)
Again, great videos as usual. Great job!
Thank you for the great videos!
is there any method for merging balances each address ?
If you use the api call:
github.com/iotaledger/iota.lib.js#getaccountdata
you can get the latest confirmed balance (= balance of ALL addresses together)
Thanks for the rapid reply. :)
If wallet has 3 address
address 0 : 1
address 1 : 1
address 2 : 1
In this case, can I send 3 IOTAs by 1 transaction ?
Thank you again! :)
Yes. If you use iota.api.sendTransfer it is automatically done. You only need to specify the receive address and the amount. The api automatically starts with address 0...N until the required amount is found. In your example it will use address 0, 1 and 2.
How're the private key and the signatueMessageFragment connected? Please explain us what a theft is doing when he found a double-use address. Thanks for your videos, you're great
A great question, however I have not yet investigated how the signature is created..
I don't understand why there are transactions which are referenced by more than 1 transaction when a NEW transaction only references tips (non-referenced transactions). Can anyone explain this to me?
Let's assume:
- The Tangle has a transactionZ (tip) with no transactions referencing it.
- Node A receives a transactionA
- Node B receives a transactionB
The nodes find tips using the Monte Carlo Random Walk algorithm.
Lets assume Node A and B find the same tip (=transactionZ) at exactly the SAME time.
Now transactionA is referencing transactionZ and transactionB is referencing transactionZ.
In this example transactionZ is referenced by 2 transactions.
But it is possible it can be referenced by more transactions (3, 4,...)
Thank you for the example. I get it now!
th-cam.com/video/M9dwwgtbbOU/w-d-xo.html - what is you have 10 addresses and 0 in the first 9, does this mean it always goes through all of them before reaching address 10, where there might be some funds, so that the transaction is successful? Am I missing something? Isn't this slowing down the transaction time?
You are correct! This is how the IOTA Light wallet (desktop) works. This wallet is stateless which means it does NOT store any information. All information is retrieved from the tangle. That is why it take times to display balance information. The current Trinity wallet (mobile) is NOT stateless, it stores information. I assume (not know for sure because the code is not public) all used addresses are stored.
Great video, thank you.
Thank you!