https://nxtforum.org/general-discussion/content-providers-nxt-account-subscription-system!/
have a read, say what you think.
have a read, say what you think.
https://nxtforum.org/general-discussion/content-providers-nxt-account-subscription-system!/
have a read, say what you think.
Sorry...don't get it :(
Sorry...don't get it :(
lol i suck at explaining things.
anyway basically make a core feature for the client to enable people to subscribe to another persons account, for a cost per defined time.
think of magazine subscriptions that gets delivered to your door steps each month for $20.
now do it on the blockchain, i subscribe and pay account number 12345 10nems per 30 days. In return i get magazines sent to my door step every 30 days.
Sorry...don't get it :(
lol i suck at explaining things.
anyway basically make a core feature for the client to enable people to subscribe to another persons account, for a cost per defined time.
think of magazine subscriptions that gets delivered to your door steps each month for $20.
now do it on the blockchain, i subscribe and pay account number 12345 10nems per 30 days. In return i get magazines sent to my door step every 30 days.
Can you explain more? At its most fundamental meaning, this doesn't need anything special, unless you are saying that an event is dependent on the clock, starting from when the coin is sent into the account and stops after x hours or x days.
You cannot put that event in the solution can you? You will need to program the event outside the block chain isn't it?
In other words you need to program anyway. Therefore might as well program and check time stamp entry of the coin into the account and you will have a neat program that relies on the block chain as a time stamp.
Sorry...don't get it :(
lol i suck at explaining things.
anyway basically make a core feature for the client to enable people to subscribe to another persons account, for a cost per defined time.
think of magazine subscriptions that gets delivered to your door steps each month for $20.
now do it on the blockchain, i subscribe and pay account number 12345 10nems per 30 days. In return i get magazines sent to my door step every 30 days.
Can you explain more? At its most fundamental meaning, this doesn't need anything special, unless you are saying that an event is dependent on the clock, starting from when the coin is sent into the account and stops after x hours or x days.
You cannot put that event in the solution can you? You will need to program the event outside the block chain isn't it?
In other words you need to program anyway. Therefore might as well program and check time stamp entry of the coin into the account and you will have a neat program that relies on the block chain as a time stamp.
instead of using time, we use no. of blocks for validity/expiration but for user interface we can interpret that no. of blocks in clock time.
Sorry...don't get it :(
lol i suck at explaining things.
anyway basically make a core feature for the client to enable people to subscribe to another persons account, for a cost per defined time.
think of magazine subscriptions that gets delivered to your door steps each month for $20.
now do it on the blockchain, i subscribe and pay account number 12345 10nems per 30 days. In return i get magazines sent to my door step every 30 days.
Can you explain more? At its most fundamental meaning, this doesn't need anything special, unless you are saying that an event is dependent on the clock, starting from when the coin is sent into the account and stops after x hours or x days.
You cannot put that event in the solution can you? You will need to program the event outside the block chain isn't it?
In other words you need to program anyway. Therefore might as well program and check time stamp entry of the coin into the account and you will have a neat program that relies on the block chain as a time stamp.
instead of using time, we use no. of blocks for validity/expiration but for user interface we can interpret that no. of blocks in clock time.
So basically what you want are sheduled tx right ?
Sorry...don't get it :(
lol i suck at explaining things.
anyway basically make a core feature for the client to enable people to subscribe to another persons account, for a cost per defined time.
think of magazine subscriptions that gets delivered to your door steps each month for $20.
now do it on the blockchain, i subscribe and pay account number 12345 10nems per 30 days. In return i get magazines sent to my door step every 30 days.
Can you explain more? At its most fundamental meaning, this doesn't need anything special, unless you are saying that an event is dependent on the clock, starting from when the coin is sent into the account and stops after x hours or x days.
You cannot put that event in the solution can you? You will need to program the event outside the block chain isn't it?
In other words you need to program anyway. Therefore might as well program and check time stamp entry of the coin into the account and you will have a neat program that relies on the block chain as a time stamp.
instead of using time, we use no. of blocks for validity/expiration but for user interface we can interpret that no. of blocks in clock time.
It is in NEM and in every coin you can do the same. ;)
This is the idea:
On the 20th of each month your health club membership is due, he wants the NEM client to pay for it automatically. So he wants to set it up in the NEM client that on the 20th of each month the NEM client will automatically send the required payment to the health club when it is due.
Having to figure this out by the number of blocks is too time consuming and hard for average joe.
This is the idea:
On the 20th of each month your health club membership is due, he wants the NEM client to pay for it automatically. So he wants to set it up in the NEM client that on the 20th of each month the NEM client will automatically send the required payment to the health club when it is due.
Having to figure this out by the number of blocks is too time consuming and hard for average joe.
Considered done at V1!! This is called rule based recurring payment.
well thats cool! can't wait for the release! ;D
btw if you read here, you should come read here as well. since my real intention for the idea is explained here.
https://forum.ournem.com/index.php?topic=2482.msg5985#msg5985
Thanks!
This is the idea:
On the 20th of each month your health club membership is due, he wants the NEM client to pay for it automatically. So he wants to set it up in the NEM client that on the 20th of each month the NEM client will automatically send the required payment to the health club when it is due.
Having to figure this out by the number of blocks is too time consuming and hard for average joe.
Considered done at V1!! This is called rule based recurring payment.
Please note that Beta != V1. Thanks!
This is cool. I like the idea :).