AC is only a week old...


i think AC0.3.0 will be stable enough to be the one that lives so long we don't want to fork it at all.


anyway.... i will keep  the exchange rate for AC0.2.0/AC0.3.0 to be 1:1

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!

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!

---

Users can call methods like this one:

Elwar(1493uAC) = Wallet[AC0M98S1|Elwar]->SendAbstractCoins( AC0m97S1|adamstgBit , 100 );

In this example, wallet "AC0M98S1|Elwar" sends wallet "AC0M98S1|adamstgBit" 100 uAC, and so,wallet "AC0M98S1|Elwar" has 1493uAC left. Users will need to quote their previous confirmed transaction in order to make a new transaction, this means all transactions will inevitably lead back to the genesis transaction. The transaction can be confirmed by anyone like this:

confirmed;



Now adamstgBit can use his new wallet( "AC0m97S1" ) in a new transaction like so:

adamstgBit(90uAC) = Wallet[AC0m97S1|adamstgBit]->SendAbstractCoins( AC0M98S1|Elwar, 10 );


Looking at this runtime call closely we can see:




This transaction can be confirmed by anyone like this:

confirmed;


When confirming a transaction it is important to get the quote right, you can remove all the irelevant text, your only confirming the transaction.

When creating a new transaction it is important to get the quote right! your very first transaction must quote the confirmed; block which shows someone sending you Abstract Coins, all subsequent transactions must quote your previous confirmed; transaction.


Users can use GetBalance, to declare their total balance.

AC0m97S1|adamstgBit(90uAC) = Wallet[AC0m97S1|adamstgBit]->GetBalance();

you must include your previous confirmed; call, for any call you do. this will create a quote chain of confirmed; transaction / calls.




To declare their wallet, anyone can say:

CreateAbstractWallet(AC0M98S1|Elwar);






AbstractCoin++ has many key words users can use.
confirmed;
runtime error(s);

More details coming soon...

---

Abstract Coin - an idea worth thinking about.

 

---

AbstractCoin++ is the programing language we will use to define the implementation of Abstract Coin! The compiler of this language is the Abstract Coin user base itself, they design the protocol, and they invoke the methods that sents 0.0001AC to other wallets. For Abstract Coin users the forum is our call stack! The calls we put up on the call stack are executed in realtime by other Abstract Coin users; you could say Abstract Coin's runtime is distributedly executed among the users minds!

Below we can see AbstractCoin's protocol, this protocol defines the interface users must use to make transactions.


/*===========================================================================
| (AbstractWallet ::SendAbstractCoins)
|
|  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 SendAbstractCoins( int SendTo_Id, int Send_Amount, int Units=uAC )=0;
  virtual float GetBalance(int Units=uAC)=0;
};
typedef std::vector<AbstractWallet> AbstractWalletList;


/*===========================================================================
| (CreateAbstractWallet)
|
|  PURPOSE: to allow an users to Create a new Abstract Wallet
|
|  RETURN: void
|    
\===========================================================================*/
void CreateAbstractWallet(int User_Id);



/*===========================================================================
| (DefaultWallet)
|
|   Return the Default Abstract Wallet for the user.  
|   When you created your first wallet, it automatically became your DefaultWallet.
|   Make a tx like this:
|
|                 Elwar(1493uAC) = DefaultWallet(Elwar)->SendAbstractCoins( DefaultWallet(adamstgBit) , 100 );
|
|  User Elwar sends user adamstgBit 100 uAC.
|    
\===========================================================================*/
AbstractWallet  DefaultWallet(int User_Id);



/*===========================================================================
| (SetDefaultWallet)
|
|   Set the Default Abstract Wallet for the user.
|
|   Make a tx like this:  User Elwar sets default Abstract Wallet
|   Elwar(1493uAC) = SetDefaultWalletWallet(AC0M98S1|Elwar);
|    
\===========================================================================*/
int SetDefaultWallet(AbstractWallet NewDefaultWallet,int User_Id);



/*===========================================================================
| (Wallet)
|
|   Wallet is a vector list of Abstract Wallets,
|   It holds everyone's wallet, make a tx like this:
|  
|                   Elwar(1493uAC) = Wallet[AC0M98S1|Elwar]->SendAbstractCoins( AC0m97S1|adamstgBit , 100 );
|    
\===========================================================================*/
AbstractWalletList  Wallet;

 

---

What is Abstract Coin?

Abstract Coin is a new type of object! It is an imaginary object. it exist because i says it does! Abstract Coin transactions can appear anywhere on this forum, simply by making a post with the right protocol. Its supply is strictly limited to 1 coin. Abstract Coins are infinitely divisible and impossible to counterfeit! They can be transfer between bitcointalk.org forum members. Abstract Coin doesn't have any particular software associated with it. Abstract Coin is nothing more then an imaginary object. Abstract Coin operates with a protocol, this protocol defines the interface users must use to make transactions.


How does Abstract Coin work?

transactions must be confirmed before recipients can send the coins to someone else. A transaction can be confirmed by anyone as long as they are not mentioned in the transaction. Quote the unconfirmed transaction and says "confirmed!". Only by quoting the confirmed transaction, can the recipient create an unconfirmed transaction. Each new unconfirmed transaction will contain the previous confirmed transaction, this will create a quote chain of confirmed transactions.
Its as simple as that!

What about double spends?

If someone sends you 0.001AC what's stopping you from quoting that post over and over sending Abstract Coins all over the forum to everyone!?
Anyone can throw a runtime error on any transaction, this calls into question the validity of that claim, if others confirm the  runtime error  then that transaction is no longer considered. just try to double spend... see what happens  

Beta Testing!

This is an experiment, for fun, lets see what happens    In theory these coins can be moved anywhere on the forum, but i would ask we keep the transactions on this thread, during beta testing.  the hope is that in the end with some tweaking to the protocol, people could place some value on these imaginary coins.  I am giving away random amounts to anyone who wants some.
post your interest below.

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

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

your right! lol

runtime errors!
lmao!



typical reaction when first looking at this thread

confirmed;
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);

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

idk

make a thread in service discussion maybe someone out there  knows all about Listentobitcoin.com