3

You can change the URL in the provider field to a node that's on the Mainnet. You can use this URL as an example: https://nodes.thetangle.org/ Or, you can run your own node. Be sure to use a minimum weight magnitude of at least 14 for the Mainnet. For example, for the code you linked to, you need to use something like the following: const provider = '...


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 ...


1

I do not hold a direct answer, I am sorry. What I would like to add is that MAM is going to be deprecated with the upcoming Chrysalis Part 2 upgrade, therefore I suggest you look into IOTA Streams, that will take over MAM: Read about the latest news in our Blog here: https://blog.iota.org/iota-streams-update-september-2020-c3b8668e231e


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

Yes exactly, each leaf is a new transaction. However, since Mam transactions do not have any “value”, they do not actually need any validation. They are immediately available to fetch after they are published


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.


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