3

It's irrelevant, you don't need a seed to publish a MAM message since you don't sign the transaction: Example: https://github.com/iota-community/javascript-iota-workshop/blob/master/code/7.1-mam-public-send.js If your library for some reason requires a seed just make one up, you can just publish to any address without the seed belonging to it. The seed is ...


3

I just tested your code and it worked for me. This is an example of the response: NVYRBTEAJAYAJMWIAHRMZNT9PQMIUWFTLQOB9RVAIWDLDOSZHPJCWEGNF9JTZLCTULRFCWFEAFAPUIMFM Published Object {numberofSteps: 14, kilometersWalked: 110, message: "Message from Alice", timestamp: "12/4/2019, 8:28:51 AM"} To do this automatically, you could set up events in the code that ...


2

Umair's answer is the correct one, but I just wanted to add that it's free to send only data in a transaction. We call this a zero-value transaction. Once a transaction is on the Tangle, anyone can read it as long as it isn't encrypted, for example using a restricted or private channel in Masked Authenticated Messaging. We recently updated the documentation ...


2

IOTA is what we call 'quantum robust' because of the signature scheme that it uses. You can find detailed information about signatures on our documentation portal.


2

IOTA in it's current state should be considered as a work in progress protocol. It can technically be used right now, but I'd advice you to use it for Proof of Concepts only at this point, at least until Coordicide has rolled out. If you want to use it for a production platform right now be prepared to do changes later on since some things will change ...


2

Compass, IOTA's open source coordinator, uses a Merkle tree to overcome the limitation that every key can only be reused once. By building a tree of possible signatures, it can sign multiple times, therefore allowing more than one milestone. The depth will determine the depth of this tree, controlling how many milestones the coordinator can sign before the ...


2

When the tip selection algorithm searches for transactions, it uses a depth parameter. You can find out more about depth here: https://docs.iota.org/docs/getting-started/0.1/transactions/depth


1

Yes, you can add new messages to a MAM stream by reloading the “mam state” and then simply publishing again. here is an example using javascript https://github.com/Evanfeenstra/helix/blob/master/mam.js#L181


1

Which operating system did you install it on? Did you configure anything so far? (for example changed any ports or added any neighbors so far?) By the way this reminds me of something similar I have opened an issue a while back https://github.com/iotaledger/iri/issues/1678 Maybe you've added a neighbor with an invalid port? Please check /etc/default/iri ...


1

As stated in the instructions, you should run the installation as root by becoming root (sudo su), else it doesn't get the correct ENVs for root. The correct link for the most up-to-date documentation is https://iri-playbook.readthedocs.io/en/feat-docker/getting-started-quickly.html Note that the command only has one <, i.e.: bash <(curl -s https://...


1

Disclaimer: I am not a developer Have you tried following this tutorial? https://hashnode.com/post/mqtt-and-mam-sending-temperature-and-humidity-data-to-the-iota-tangle-ck4wbbzap01artjs1t5dfog2t Comparing the code might help.


1

Mam.fetch is not an async function, instead use the callback. You can make any “callback style” function into an async function by wrapping the call in a return new Promise((resolve,reject)=> .... Do a bit of research about Promises, this is a very common and useful pattern in Nodejs. But i think your problem is secretKey needs to be converted to trytes


1

You just run Mam.fetch. You need to store the root somewhere, and the sideKey if you are using “restricted” mode.


1

What library do you use? You can check, if the transaction is referenced by a milestone. This is the ultimate confirmation for your transaction. If the milestone directly or indirectly confirms your transaction, the transaction is received by all full-nodes.


1

You can use official client libraries for sending transactions to the tangle. Here is an example of sending data to the tangle. An example of reading transactions from the tangle can be found here.


1

As the whole implementation uses ternary arithmetic, it uses ternary algorithms. For hashing there are three ternary algorithms in use or planned to be used: CURL-T (the original one) where weaknesses were found and therefore it is now only used for Proof of Work KERL, which is basically a ternary wrapper around Keccak (SHA-3) and which is used for all ...


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