Topic: [Experiment] Abstract Coin 0.2.1 - page 3. (Read 9119 times)
You should really create a testnet. If you want I can do that for you.
Your "runtime" is ridiculous.
The older protocol was fine.
The older protocol was fine.
no I'm leaving this fork to dust in a few today... maybe hours...
if you want a % of the initial AC0.3.0 you'll have to adhere to AC0.3.0's protocol.
I'm not sure it can be left as it is out there and ITT
also you should fork to AC0.3.0
AC0.3.0 will be open on the 10th 8:00PM EST
the genesis block will be declared and i will start giving away the coins to everyone
i plan to give away a good %80-90 of the coins in the first few days..
some % is for people that have help me alot along the way, the more you contribute the more AC i will give you. contributing is as simple as calling SendTx(); correctly, and having fun!
Your "runtime" is ridiculous.
The older protocol was fine.
The older protocol was fine.
no I'm leaving this fork to dust in a few today... maybe hours...
if you want a % of the initial AC0.3.0 you'll have to adhere to AC0.3.0's protocol.
I'm not sure it can be left as it is out there and ITT
also you should fork to AC0.3.0
On day 1, somone edited their post and claimed that they only sent me 0.001 not 0.05 .... this act killed Abstract Coin 0.1.0;
i hope Abstract Coin 0.3.1 will be stable enoght to live forever!
sucks we had to kill Abstract Coin 0.2.1 it was going so good!
but this is for the best.
Abstract Coin - Adhere to the Protocol!
i hope Abstract Coin 0.3.1 will be stable enoght to live forever!
sucks we had to kill Abstract Coin 0.2.1 it was going so good!
but this is for the best.
Abstract Coin - Adhere to the Protocol!
Your "runtime" is ridiculous.
The older protocol was fine.
The older protocol was fine.
no I'm leaving this fork to dust in a few today... maybe hours...
if you want a % of the initial AC0.3.0 you'll have to adhere to AC0.3.0's protocol.
its probably time to scrap all the old Abstract Coin 0.2.1 and make a new version of Abstract Coin, Abstract Coin 0.3.0
i have a feeling people are going to panic sell
Abstract Coin 0.2.1 is about to become COMPLETELY worthless!!!
i have a feeling people are going to panic sell
Abstract Coin 0.2.1 is about to become COMPLETELY worthless!!!
I think for now
(u)(49750)|jubalix|ACICAHJFKJ|(-50)(R)(49700) ------>(u)(+50)|test|test|
is ok, and will do, most people can get this.....
no i really want the C++ feel to it.
trust me i'm not the only one that first started coding in C, around here...
people love C++
CreateAbstractWallet(ACC0M420|adamstgBit);
jubalix(49600uAC) = AbstractWalletList[jubalix|ACICAHJFKJ]->sendTx( ACC0M420|adamstgBit , 100uAC );
runtime error(2);
"the host wallet could not be identified - use void CreateAbstractWallet(int User_Id); to make a new wallet "
"must include your last tx as part of your next tx with a quote, it is preferable that you quote a confirmed tx"
ah but that wallet already exists instantiated by older code, (also I am not going to risk resetting it to zero with a new instantiation)
your right! lol
I think for now
(u)(49750)|jubalix|ACICAHJFKJ|(-50)(R)(49700) ------>(u)(+50)|test|test|
is ok, and will do, most people can get this.....
CreateAbstractWallet(ACC0M420|adamstgBit);
jubalix(49600uAC) = AbstractWalletList[jubalix|ACICAHJFKJ]->sendTx( ACC0M420|adamstgBit , 100uAC );
runtime error(2);
"the host wallet could not be identified - use void CreateAbstractWallet(int User_Id); to make a new wallet "
"must include your last tx as part of your next tx with a quote, it is preferable that you quote a confirmed tx"
ah but that wallet already exists instantiated by older code, (also I am not going to risk resetting it to zero with a new instantiation)
your compiler is not properly depreciated/backwards compatible
Your "runtime" is ridiculous.
The older protocol was fine.
The older protocol was fine.
CreateAbstractWallet(ACC0M420|adamstgBit);
jubalix(49600uAC) = AbstractWalletList[jubalix|ACICAHJFKJ]->sendTx( ACC0M420|adamstgBit , 100uAC );
runtime error(2);
"the host wallet could not be identified - use void CreateAbstractWallet(int User_Id); to make a new wallet "
"must include your last tx as part of your next tx with a quote, it is preferable that you quote a confirmed tx"
CreateAbstractWallet(ACC0M420|adamstgBit);
jubalix(49600uAC) = AbstractWalletList[jubalix|ACICAHJFKJ]->sendTx( ACC0M420|adamstgBit , 100uAC );
i like that you improved the protocol, its definitely getting better, maybe we should make the protocol look like C++ code 
here is the interface i would like us to use
/*===========================================================================
| sendTx:
|
| PURPOSE: to allow an AbstractWallet to send an amount of AC to another AbstractWallet.
|
| RETURN: int value, the Amount of uAC left in the sender wallet.
|
\===========================================================================*/
class AbstractWallet {
virtual int sendTx( int SendTo_Id, int Send_Amount)=0;
};
typedef std::vector AbstractWalletList;
void CreateAbstractWallet(int SendTo_Id);
now we can push a tx like this
tadakaluri(1493uAC) = AbstractWalletList[AC0M98S1|tadakaluri]->sendTx( AC0m97S1|adamstgBit , 100 );
do you get it??
wallet "AC0M98S1|tadakaluri"
sends
wallet "AC0M98S1|adamstgBit" 100 uAC
and
wallet "AC0M98S1|tadakaluri"
has 1493uAC left
and anyone can say something like:
CreateAbstractWallet(AC0M98S1|tadakaluri);
to declare their wallet...
here is the interface i would like us to use
/*===========================================================================
| sendTx:
|
| PURPOSE: to allow an AbstractWallet to send an amount of AC to another AbstractWallet.
|
| RETURN: int value, the Amount of uAC left in the sender wallet.
|
\===========================================================================*/
class AbstractWallet {
virtual int sendTx( int SendTo_Id, int Send_Amount)=0;
};
typedef std::vector
void CreateAbstractWallet(int SendTo_Id);
now we can push a tx like this
tadakaluri(1493uAC) = AbstractWalletList[AC0M98S1|tadakaluri]->sendTx( AC0m97S1|adamstgBit , 100 );
do you get it??
wallet "AC0M98S1|tadakaluri"
sends
wallet "AC0M98S1|adamstgBit" 100 uAC
and
wallet "AC0M98S1|tadakaluri"
has 1493uAC left
and anyone can say something like:
CreateAbstractWallet(AC0M98S1|tadakaluri);
to declare their wallet...
this is ok.....I have always liked explicit variables to check, read code and provide information which is why I provide
View Profile Email Personal Message (Online)
8-13 ignores
Re: [Experiment] Abstract Coin 0.2.1
Today at 02:27:32 AM
Reply with quote Edit message Delete message #193
Quote from: Invest0r on Today at 02:15:47 AM
I'd like some Smiley
Just created a wallet:
|ACINVEST0|
(u)(49750)|jubalix|ACICAHJFKJ|(-50)(R)(49700) ------>(u)(+50)|test|test|
units on both sides and the whole equation being
my ballance, amount sent with sign, (R) for return and amount after and on the other side amount sent.
so
I may suggest
we have int's for current amounts and send an received......it makes it really easy to read, and double if not triple check.
tadakaluri(1493uAC) = AbstractWalletList[AC0M98S1|tadakaluri]->sendTx( AC0m97S1|adamstgBit , 100 );
new ACwallet(|jubalix|ACICAHJFKJ|,n); (n for nano = default, you could override)
ACwallet::SendNow
class sendNow{SendWallet, Ballance, unit, amount,Receive Wallet)
{send-->Tx}
anyway I am sure something can be figured out....good idea though
CreateAbstractWallet(ACC0M420|adamstgBit);
i like that you improved the protocol, its definitely getting better, maybe we should make the protocol look like C++ code
here is the interface i would like us to use
/*===========================================================================
| sendTx:
|
| PURPOSE: to allow an AbstractWallet to send an amount of AC to another AbstractWallet.
|
| RETURN: int value, the Amount of uAC left in the sender wallet.
|
\===========================================================================*/
class AbstractWallet {
virtual int sendTx( int SendTo_Id, int Send_Amount)=0;
};
typedef std::vector AbstractWalletList;
void CreateAbstractWallet(int SendTo_Id);
now we can push a tx like this
tadakaluri(1493uAC) = AbstractWalletList[AC0M98S1|tadakaluri]->sendTx( AC0m97S1|adamstgBit , 100 );
do you get it??
wallet "AC0M98S1|tadakaluri"
sends
wallet "AC0M98S1|adamstgBit" 100 uAC
and
wallet "AC0M98S1|tadakaluri"
has 1493uAC left
and anyone can say something like:
CreateAbstractWallet(AC0M98S1|tadakaluri);
to declare their wallet...
here is the interface i would like us to use
/*===========================================================================
| sendTx:
|
| PURPOSE: to allow an AbstractWallet to send an amount of AC to another AbstractWallet.
|
| RETURN: int value, the Amount of uAC left in the sender wallet.
|
\===========================================================================*/
class AbstractWallet {
virtual int sendTx( int SendTo_Id, int Send_Amount)=0;
};
typedef std::vector
void CreateAbstractWallet(int SendTo_Id);
now we can push a tx like this
tadakaluri(1493uAC) = AbstractWalletList[AC0M98S1|tadakaluri]->sendTx( AC0m97S1|adamstgBit , 100 );
do you get it??
wallet "AC0M98S1|tadakaluri"
sends
wallet "AC0M98S1|adamstgBit" 100 uAC
and
wallet "AC0M98S1|tadakaluri"
has 1493uAC left
and anyone can say something like:
CreateAbstractWallet(AC0M98S1|tadakaluri);
to declare their wallet...
in essence this is like a new programing language "AbstractCoin++"
This fourm is the RUNTIME! and we interact with the runtime directly
i like that you improved the protocol, its definitely getting better, maybe we should make the protocol look like C++ code
here is the interface i would like us to use
/*===========================================================================
| sendTx:
|
| PURPOSE: to allow an AbstractWallet to send an amount of AC to another AbstractWallet.
|
| RETURN: int value, the Amount of uAC left in the sender wallet.
|
\===========================================================================*/
class AbstractWallet {
virtual int sendTx( int SendTo_Id, int Send_Amount)=0;
};
typedef std::vector AbstractWalletList;
void CreateAbstractWallet(int SendTo_Id);
now we can push a tx like this
tadakaluri(1493uAC) = AbstractWalletList[AC0M98S1|tadakaluri]->sendTx( AC0m97S1|adamstgBit , 100 );
do you get it??
wallet "AC0M98S1|tadakaluri"
sends
wallet "AC0M98S1|adamstgBit" 100 uAC
and
wallet "AC0M98S1|tadakaluri"
has 1493uAC left
and anyone can say something like:
CreateAbstractWallet(AC0M98S1|tadakaluri);
to declare their wallet...
here is the interface i would like us to use
/*===========================================================================
| sendTx:
|
| PURPOSE: to allow an AbstractWallet to send an amount of AC to another AbstractWallet.
|
| RETURN: int value, the Amount of uAC left in the sender wallet.
|
\===========================================================================*/
class AbstractWallet {
virtual int sendTx( int SendTo_Id, int Send_Amount)=0;
};
typedef std::vector
void CreateAbstractWallet(int SendTo_Id);
now we can push a tx like this
tadakaluri(1493uAC) = AbstractWalletList[AC0M98S1|tadakaluri]->sendTx( AC0m97S1|adamstgBit , 100 );
do you get it??
wallet "AC0M98S1|tadakaluri"
sends
wallet "AC0M98S1|adamstgBit" 100 uAC
and
wallet "AC0M98S1|tadakaluri"
has 1493uAC left
and anyone can say something like:
CreateAbstractWallet(AC0M98S1|tadakaluri);
to declare their wallet...
I'd like some
Just created a wallet:
|ACINVEST0|
Just created a wallet:
|ACINVEST0|
(u)(49750)|jubalix|ACICAHJFKJ|(-50)(R)(49700) ------>(u)(+50)|Invest0r|ACINVEST0|
I'd like some
Just created a wallet:
|ACINVEST0|
Just created a wallet:
|ACINVEST0|
Jump to: