Hi
Our project LCNEM is all progressing smoothly.
lcnem.cc
To know LCNEM, please see our website.
In short, we issue mosaics which are pegged with legal currencies.
To make our project successful, NEM mobile wallet must support multiassets.
However, when will it be released is unclear.
So, I think two things.
- I want to support core developers in anyway
- I want NEMbers to determine the JSON object structure of invoice which supports multiassets because LCNEM want to make payments with LCNEM mosaics popular.
Now, we can use an invoice by reading with QR code reader. But now it doesn’t support multiassets.
The current JSON object structure is this.
{
“v”:2,
“type”:2,
“data”:
{
“addr”:"",
“amount”:1000000,
“msg”:"",
“name”:""
}
}
This invoice can’t support multiassets, and LCNEM will be in trouble because we can’t promote LCNEM mosaics payment.
So, I propose this JSON object structure.
{
“v”:2,
“tvpe”:2,
“data”:{
“name”:"",
“addr”:"",
“msg”:"",
“assets”:[
{
“mosaic”:“nem:xem”,
“amount”:1000000
},
{
“mosaic”:“lc:1000jpy”,
“amount”:1000
}
]
}
}
Ofcourse, this is no more than a proposal.
However, I want NEMbers to determine the next generation JSON object structure of invoice.
If you think this problem, LCNEM payment can lay the groundwork.
Thanks