Bitcoin Forum
December 18, 2017, 03:13:49 PM *
News: Latest stable version of Bitcoin Core: 0.15.1  [Torrent].
 
  Home Help Search Donate Login Register  
  Show Posts
Pages: [1] 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 ... 54 »
1  Bitcoin / Pools / Re: [14000Th] Eligius: 0% Fee BTC, 105% PPS NMC, No registration, CPPSRB on: January 09, 2017, 05:15:51 PM
Thanks for the update! When will the new stats be live?
2  Economy / Digital goods / Re: FANDUEL ACCOUNTS FOR SALE WITH HIGH BALANCES TRADE FOR BTC!! on: November 04, 2015, 08:47:26 PM
Why are you selling accounts? I don't understand.
3  Economy / Currency exchange / Re: Buying BTC---LONG TERM---PP/MB/NT/PAYZA/AGC/WU/XOOM/MG/AP/MP/GW/SqC/DWOLLA/WIRE on: May 08, 2014, 09:02:29 PM
Checkout process is simple/easy, I got PP for BTC.
4  Economy / Auctions / Re: [ANN] BTCTK.com auction - being sold on: May 08, 2014, 05:59:16 PM
Based on your trust rating what stops you from reselling the source code?

You can search my posts and investigate why I was given a negative trust and I was given negative trust by some guy trying to blackmail my casino into paying him BTC.

I am now waiting for 1BTC from the buyer, if he changes his mind I would relaunch the auction.

False.

https://bitcointalk.org/index.php?topic=278895.20
5  Economy / Scam Accusations / Re: SCAMMER TAG REQUEST - CASINOBIT.NET IS NOT PAYING OUT INVESTORS on: March 28, 2014, 06:47:52 PM
Here is another sock puppet: https://bitcointalk.org/index.php?topic=543237.0;topicseen
6  Economy / Currency exchange / Re: WTB 0.9BTC For Paypal | Will go first - trusted only on: March 28, 2014, 02:58:10 PM
I am looking to buy about 1BTC for Paypal, already have a good trading history on here, traded with two sellers BurtW and cryptocap in the same manner before.

Willing to send the payment before receiving BTC.

Ignore the bad rep, some guy tried to extort money. Cheers.

False.
7  Alternate cryptocurrencies / Altcoin Discussion / Re: Q&A: i0coin and iXcoin on: March 28, 2014, 02:53:42 PM
Thanks for the help gents. I will clean up the Q&A as I'm able.

What would you add to the list? What distinguishing features do you want forum members and the general public to know about these coins?

What are some ideas/thoughts going forward in the development of these coins? Are most current challenges practical/participatory i.e. need more demand, more pools, more exchanges?
8  Alternate cryptocurrencies / Altcoin Discussion / Re: Q&A: i0coin and iXcoin on: March 28, 2014, 02:26:40 PM

Q: Why is the blockcount of i0coin so much higher than IXcoin?
A:  i0coin block rate is 4 times that of iXcoin (10 minutes)

Q: What happened (if anything) to i0coin when it was hard-forked? What happened when it "died" early in its life?
A:

Q: What happened to the 7? million pre-mined IXcoins?
A:  Around 500,000 coins were pre-mined.   The original developer claims that 50% of that was spent on bounties.

Q: Who now controls the development of these coins?
A: No official,  however the github source code of the latest version is public.

Q: What unique security concerns exist for these two coins?
A:

Q: What distinguishes a "mature" alt-coin from new, "immature" brethren?
A:  iXcoin has been around for 3 years without issue,  furthermore it is among the top 4 in hash rate among all coins.

Q: Are these coins compatible with most bitcoin purchasing hardware, atms, etc.?
A: It uses a different block chain, but the creation of transactions are similar.

Q: Will pools drop these coins when rewards are tx fee-only?
A: This is unknown.

Q: What compelling reason do pools have to merge mine the coins if transaction fees, coin activity, and coin value are low?
A: iXcoin has been merged mined most of its life.   We have not seen a drop off in  mining.

Q: How does scarcity affect value, absent much demand?
A: Demand is certainly an issue with iXcoin.  We hope innovation will spur demand.

Q: Why is IXCoin currently worth more than I0Coin?
A:  There are more I0coin,  I0coin is traded in only one exchange,  iXcoin has a massive hash rate that dwarfs I0Coin.


TY, Sir!

What is the state of development with IXCoin, I see you handle the website, what are other plans for the coin?
9  Alternate cryptocurrencies / Altcoin Discussion / Re: Q&A: i0coin and iXcoin on: March 26, 2014, 04:47:00 PM
Ah, the original scam coins...

Can you explain the meaning of "scam coin"?
10  Alternate cryptocurrencies / Altcoin Discussion / Q&A: i0coin and iXcoin on: March 26, 2014, 03:05:49 PM
With i0coin quickly approaching 21 million coins, I thought it would be appropriate to explore the situation between i0 and iX as well as coin value and security with transaction-fee-only rewards. I will keep this thread up-to-date with answers to my own personal questions as well as other questions readers might have. Please pose your question like the format below.

Q: Why is the blockcount of i0coin so much higher than IXcoin?
A: i0coin block rate is 4 times that of iXcoin (10 minutes).

Q: What happened (if anything) to i0coin when it was hard-forked? What happened when it "died" early in its life?
A: I0coin was updated to bitcoin 0.8.x base. It fixed some issues, like the asymmetric diffuculty adjustment, block size limits and BIP16/BIP30 IIRC (see original resurrection thread i0coin.snel.it) It 'died' because the client used too much memory, people (and exchanges) didn't want to run it. It was kept alive by a small group of people until I fixed the memory issue.

Q: What happened to the pre-mined IXcoins?
A: Around 500,000 coins were pre-mined. The original developer claims that 50% of that was spent on bounties. The rest is unknown.

Q: Who now controls the development of these coins?
A: Rsnel is the i0coin developer and FrictionlessCoin is the iXcoin contact (no official developer.)

Q: What unique security concerns exist for these two coins?
A: IXcoin had (has?) asymmetric difficulty adjustment, which allows 51% attackers to produce more blocks than they should be able to. Also: hashrate is available to attackers without opportunity cost, because they can mine bitcoin and attack IXcoin I0coin at the same time. Large pools can do this attack trivially on I0coin since the hashrate is far behind.

Q: What distinguishes a i0 and iX from new, "immature" altcoins?
A: i0/IX have cloned bitcoin functionality and accelerated the rate of coin production using massive SHA256 hashpower. Many other altcoins utilize scrypt and are vulnerable after their "hype" ends when their hashrate drops.

Q: Are these coins compatible with most bitcoin purchasing hardware, atms, etc.?
A: They should be compatible as long as the device/service is utilizing the i0/IX blockchain.

Q: Will pools drop these coins when rewards are tx fee-only?
A:

Q: What compelling reason do pools have to merge mine the coins if transaction fees, coin activity, and coin value are low?
A: iXcoin has been merged mined most of its life. We have not seen a drop off in  mining. Free extras are always nice. Some pools seem to be afraid that the high blockrate of I0coin damages the efficiency of BTC mining, a good implementation of merged mining can't suffer from the high blockrate.

Q: Why is IXCoin currently worth more than I0Coin?
A: There are more I0coin. I0coin is traded in only one exchange. iXcoin has a massive hash rate that dwarfs I0Coin.

Coin Stats as of 3/28

Bitcoin
Total Coins: 21 Million
Coins/Block:
Blockcount:
Current Coins:
Current Hashrate:
Avg. Block Time:
IXCoin
Total Coins:
Coins/Block:
Blockcount:
Current Coins:
Current Hashrate:
Avg. Block Time:
I0Coin
Total Coins:
Coins/Block:
Blockcount:
Current Coins:
Current Hashrate:
Avg. Block Time:
11  Alternate cryptocurrencies / Altcoin Discussion / Re: [LTC] Changing the litecoin Proof of Work function to avoid ASIC mining? on: March 19, 2014, 09:04:41 PM
too late?
12  Alternate cryptocurrencies / Announcements (Altcoins) / Re: [ANN][FSC] FusionCoin | Dual PoW(SHA256&Scrypt) | Both Merged Minable on: March 17, 2014, 04:53:04 PM
This isn't compiling properly on ubuntu 12.04

sudo make -f makefile.unix fusioncoind

errors out... what dependencies are needed?

It was caused by missing executable permission of "leveldb/build_detect_platform".
Fixed.
git pull or manually
Code:
chmod +x leveldb/build_detect_platform

Thanks. It works now.
13  Alternate cryptocurrencies / Announcements (Altcoins) / Re: [ANN][FSC] FusionCoin | Dual PoW(SHA256&Scrypt) | Both Merged Minable on: March 17, 2014, 02:29:54 PM
This isn't compiling properly on ubuntu 12.04

sudo make -f makefile.unix fusioncoind

errors out... what dependencies are needed?
14  Alternate cryptocurrencies / Altcoin Discussion / Re: [DEAD] Coiledcoin - yet another cryptocurrency, but with OP_EVAL! on: March 14, 2014, 02:40:48 PM
Can someone (Luke? Mark?) elaborate on the problem Luke described as a result of the attack? Are all blocks prior to Luke's attack invalid/unspendable, or is it just his blocks? How many blocks are we talking about?

I show the current block count as just above 400k, which is short of what it should be according to makomk's target.

-Eric
15  Alternate cryptocurrencies / Mining (Altcoins) / Re: [OFFLINE]P2Pmining.com-Hybrid P2Pool-NO FEE!!!-BTC/NMC/IXC/I0C/DEV/LTC on: March 14, 2014, 02:03:11 PM
I have a bunch of fixes to push out this weekend.  I tested on terracoin and with more blocks being found, I found more bugs. I will be moving functions that are not for logging shares to another script so that any problems with the other functions won't bog down p2pool.

Also, the new fork is giving me this error, but might be from my changes:

2014-03-13 17:01:16.011113 1054: Unknown column 'cointype' in 'where clause'
2014-03-13 17:01:16.012629 1054: Unknown column 'cointype' in 'field list'

The newer code fixes this issue.

Ahh, nice!

FYI: I have added groupcoin and coiledcoin to the configure.py and it merges just fine. I am still working on huntercoin and geistgeld.

Off the top of your head, where would be the best place in database.py to put:

Code:
self.workDBcursor.execute("INSERT INTO miner_data (id,address,hashrate,timestamp,difficulty,ontime) VALUES (NULL, %s, %s, UNIX_TIMESTAMP(), %s, %s)",(user[:36],difficulty * on_time,difficulty,on_time))

or do you have plans on doing a front-end?
16  Alternate cryptocurrencies / Mining (Altcoins) / Re: [OFFLINE]P2Pmining.com-Hybrid P2Pool-NO FEE!!!-BTC/NMC/IXC/I0C/DEV/LTC on: March 14, 2014, 01:06:54 PM
Also, the new fork is giving me this error, but might be from my changes:

2014-03-13 17:01:16.011113 1054: Unknown column 'cointype' in 'where clause'
2014-03-13 17:01:16.012629 1054: Unknown column 'cointype' in 'field list'
17  Alternate cryptocurrencies / Mining (Altcoins) / Re: [OFFLINE]P2Pmining.com-Hybrid P2Pool-NO FEE!!!-BTC/NMC/IXC/I0C/DEV/LTC on: March 14, 2014, 01:04:56 PM
Hey Jay,
I could never get work.py to spit anything out into the miner_data database, tried multiple versions of p2pool (including freicoin version, and the build just before stratum was introduced) and multiple ways to write the SQL insert code. update_blocks / grab_data updates this table, but without difficulty/ontime data. Your new fork does this, however. I've fiddled with the code adding the SQL Insert to get it to populate miner_data in the old database to run the old front-end. I need a small amount of help to figure out where the code should be placed in database.py, I just put it everywhere an execute insert was located.

Code:
class P2PminingData:
    def __init__(self):
        try:
            self.workDB = mysql.connector.connect(user=configure.db_username,password=configure.db_password,host=configure.db_location,database=configure.db_name)
            self.autocommit = False
            self.workDBcursor = self.workDB.cursor()
             
        except mysql.connector.Error as err:
            print(err)
        self.bitcoin = bitcoin.Bitcoin(configure.args)
   
    def add_shares(self,user,difficulty,on_time):
        try:
           [b] self.workDBcursor.execute("INSERT INTO miner_data (id,address,hashrate,timestamp,difficulty,ontime) VALUES (NULL, %s, %s, UNIX_TIMESTAMP(), %s, %s)",(user[:36],difficulty * on_time,difficulty,on_time))[/b]
            self.workDBcursor.execute("""INSERT INTO live_shares (id,userid,shares) VALUES (NULL, %s , %s ) ON DUPLICATE KEY UPDATE shares=shares + %s""", (user[:36], difficulty * on_time, difficulty * on_time) )
            self.workDB.commit()
        except mysql.connector.Error as err:
            self.workDB.rollback()
            print(err)
   
    def check_for_shift_completion(self):
        try:
            self.workDBcursor.execute("SELECT sum(shares) AS share_total FROM live_shares")
            returned = self.workDBcursor.fetchone()
            if (0 if returned[0] is None else int(returned[0])) > configure.shares_per_shift:
                self.workDBcursor.execute("SELECT * FROM live_shares")
                returned = self.workDBcursor.fetchall()
                self.workDBcursor.execute("INSERT INTO shifts (id, timestamp, shiftpay, lastblockheight, confirmed) VALUES (NULL, UNIX_TIMESTAMP(), '0', '0', FALSE)")
                shift_id = self.workDBcursor.lastrowid
                for row in returned:
                    self.workDBcursor.execute("INSERT INTO shift_data (id,userid,shares,shiftid) VALUES (NULL, %s, %s, %s)", (row[1],row[2],shift_id))
                self.workDBcursor.execute("UPDATE live_shares SET shares = '0'")
                [b]self.workDBcursor.execute("INSERT INTO miner_data (id,address,hashrate,timestamp,difficulty,ontime) VALUES (NULL, %s, %s, UNIX_TIMESTAMP(), %s, %s)",(user[:36],difficulty * on_time,difficulty,on_time))[/b]
                self.workDB.commit()
        except mysql.connector.Error as err:
            self.workDB.rollback()
            print(err)
   
    def record_p2pool_share(self,user,difficulty,on_time):
        try:
            [b]self.workDBcursor.execute("INSERT INTO miner_data (id,address,hashrate,timestamp,difficulty,ontime) VALUES (NULL, %s, %s, UNIX_TIMESTAMP(), %s, %s)",(user[:36],difficulty * on_time,difficulty,on_time))[/b]
            self.workDBcursor.execute("INSERT INTO p2pool_shares (id,userid,share_hash,on_time,timestamp) VALUES (NULL, %s, %s, %s, UNIX_TIMESTAMP())",(user[:36],share_hash,on_time))
            self.workDB.commit()
        except mysql.connector.Error as err:
            self.workDB.rollback()
            print(err)   
   
    def record_block_from_miner(self,user,block_hash,on_time):
        try:
            [b]self.workDBcursor.execute("INSERT INTO miner_data (id,address,hashrate,timestamp,difficulty,ontime) VALUES (NULL, %s, %s, UNIX_TIMESTAMP(), %s, %s)",(user[:36],difficulty * on_time,difficulty,on_time))[/b]
            self.workDBcursor.execute("INSERT INTO found_blocks (id,userid,block_hash,on_time,timestamp) VALUES (NULL, %s, %s, %s, UNIX_TIMESTAMP())",(user[:36],block_hash,on_time))
            self.workDB.commit()
        except mysql.connector.Error as err:
            self.workDB.rollback()
            print(err)

Also, I've modified the SQL database creation from what was posted earlier with a few fixes, using some settings from Jay's new database creation script. I think I've got all references to the database host / username / password / name referenced back to cred.php in the original. I'll post that when confirmed working.

Code:
CREATE TABLE `pool_blocks` (
  `id` bigint(20) NOT NULL AUTO_INCREMENT,
  `timestamp` int(11) NOT NULL,
  `time` timestamp NOT NULL DEFAULT CURRENT_TIMESTAMP ON UPDATE CURRENT_TIMESTAMP,
  `txid` varchar(64) NOT NULL DEFAULT 'NONE',
  `type` varchar(64) NOT NULL,
  `amount` decimal(16,8) NOT NULL,
  `confirmations` int(11) NOT NULL,
  `blk_num` varchar(64) NOT NULL,
  PRIMARY KEY (`id`)
) ENGINE=InnoDB DEFAULT CHARSET=latin1 AUTO_INCREMENT=1 ;

CREATE TABLE `miner_data` (
  `id` bigint(20) NOT NULL AUTO_INCREMENT,
  `address` varchar(48) NOT NULL,
  `hashrate` varchar(64) NOT NULL,
  `timestamp` int(11) NOT NULL,
  `difficulty` bigint(20) NOT NULL,
  `ontime` tinyint(1) NOT NULL,
  PRIMARY KEY (`id`)
) ENGINE=InnoDB DEFAULT CHARSET=latin1 AUTO_INCREMENT=1 ;

CREATE TABLE `miner_hist` (
  `id` bigint(20) NOT NULL AUTO_INCREMENT,
  `address` varchar(48) NOT NULL,
  `hashrate` varchar(64) NOT NULL,
  `timestamp` int(11) NOT NULL,
  `difficulty` bigint(20) NOT NULL,
  `ontime` tinyint(1) NOT NULL,
  PRIMARY KEY (`id`)
) ENGINE=InnoDB DEFAULT CHARSET=latin1 AUTO_INCREMENT=1 ;

CREATE TABLE `pay_address` (
  `address` varchar(48) NOT NULL,
  `paddress` varchar(48) NOT NULL,
  PRIMARY KEY (`address`)
) ENGINE=InnoDB DEFAULT CHARSET=latin1 AUTO_INCREMENT=1 ;

CREATE TABLE `payouts` (
  `id` bigint(20) NOT NULL AUTO_INCREMENT,
  `timestamp` int(11) NOT NULL,
  `time` timestamp NOT NULL DEFAULT CURRENT_TIMESTAMP ON UPDATE CURRENT_TIMESTAMP,
  `address` varchar(48) NOT NULL,
  `amount` decimal(16,8) NOT NULL,
  `txid` varchar(64) NOT NULL DEFAULT 'NONE',
  `paddress` varchar(48) NOT NULL,
  `paid` varchar(36) NOT NULL,
  PRIMARY KEY (`id`)
) ENGINE=InnoDB DEFAULT CHARSET=latin1 AUTO_INCREMENT=1 ;

CREATE TABLE `pool_data` (
  `id` bigint(20) NOT NULL AUTO_INCREMENT,
  `timestamp` int(11) NOT NULL,
  `time` timestamp NOT NULL DEFAULT CURRENT_TIMESTAMP ON UPDATE CURRENT_TIMESTAMP,
  `hashrate` varchar(64) NOT NULL,
  `shares` bigint(20) NOT NULL,
  `stale_doa` bigint(20) NOT NULL,
  `stale_orphan` bigint(20) NOT NULL,
  `p2pool_hashrate` bigint(20) NOT NULL,
  `p2pool_stale_rate` bigint(20) NOT NULL,
  `block_value` decimal(16,8) NOT NULL,
  `peers_out` int(11) NOT NULL,
  `peers_in` int(11) NOT NULL,
  `current_payout` decimal(16,8) NOT NULL,
  PRIMARY KEY (`id`)
) ENGINE=InnoDB DEFAULT CHARSET=latin1 AUTO_INCREMENT=1 ;

CREATE TABLE `signtime` (
  `address` varchar(48) NOT NULL,
  `timestamp` int(11) NOT NULL,
  `time` timestamp NOT NULL DEFAULT CURRENT_TIMESTAMP ON UPDATE CURRENT_TIMESTAMP,
  PRIMARY KEY (`address`)
) ENGINE=InnoDB DEFAULT CHARSET=latin1 AUTO_INCREMENT=1 ;

CREATE TABLE `lminer_data` (
  `id` bigint(20) NOT NULL AUTO_INCREMENT,
  `address` varchar(48) NOT NULL,
  `hashrate` varchar(64) NOT NULL,
  `timestamp` int(11) NOT NULL,
  `difficulty` bigint(20) NOT NULL,
  `ontime` tinyint(1) NOT NULL,
  PRIMARY KEY (`id`)
) ENGINE=InnoDB DEFAULT CHARSET=latin1 AUTO_INCREMENT=1 ;

CREATE TABLE `lminer_hist` (
  `id` bigint(20) NOT NULL AUTO_INCREMENT,
  `address` varchar(48) NOT NULL,
  `hashrate` varchar(64) NOT NULL,
  `timestamp` int(11) NOT NULL,
  `difficulty` bigint(20) NOT NULL,
  `ontime` tinyint(1) NOT NULL,
  PRIMARY KEY (`id`)
) ENGINE=InnoDB DEFAULT CHARSET=latin1 AUTO_INCREMENT=1 ;

CREATE TABLE `lpayouts` (
  `id` bigint(20) NOT NULL AUTO_INCREMENT,
  `timestamp` int(11) NOT NULL,
  `time` timestamp NOT NULL DEFAULT CURRENT_TIMESTAMP ON UPDATE CURRENT_TIMESTAMP,
  `address` varchar(48) NOT NULL,
  `amount` decimal(16,8) NOT NULL,
  `txid` varchar(64) NOT NULL DEFAULT 'NONE',
  `paddress` varchar(48) NOT NULL,
  `paid` varchar(36) NOT NULL,
  PRIMARY KEY (`id`)
) ENGINE=InnoDB DEFAULT CHARSET=latin1 AUTO_INCREMENT=1 ;

CREATE TABLE `lpool_blocks` (
  `id` bigint(20) NOT NULL AUTO_INCREMENT,
  `timestamp` int(11) NOT NULL,
  `time` timestamp NOT NULL DEFAULT CURRENT_TIMESTAMP ON UPDATE CURRENT_TIMESTAMP,
  `txid` varchar(64) NOT NULL DEFAULT 'NONE',
  `type` varchar(64) NOT NULL,
  `amount` decimal(16,8) NOT NULL,
  `confirmations` int(11) NOT NULL,
  `blk_num` varchar(64) NOT NULL,
  PRIMARY KEY (`id`)
) ENGINE=InnoDB DEFAULT CHARSET=latin1 AUTO_INCREMENT=1 ;

CREATE TABLE `lpool_data` (
  `id` bigint(20) NOT NULL AUTO_INCREMENT,
  `timestamp` int(11) NOT NULL,
  `time` timestamp NOT NULL DEFAULT CURRENT_TIMESTAMP ON UPDATE CURRENT_TIMESTAMP,
  `hashrate` varchar(64) NOT NULL,
  `shares` bigint(20) NOT NULL,
  `stale_doa` bigint(20) NOT NULL,
  `stale_orphan` bigint(20) NOT NULL,
  `p2pool_hashrate` bigint(20) NOT NULL,
  `p2pool_stale_rate` bigint(20) NOT NULL,
  `block_value` decimal(16,8) NOT NULL,
  `peers_out` int(11) NOT NULL,
  `peers_in` int(11) NOT NULL,
  `current_payout` decimal(16,8) NOT NULL,
  PRIMARY KEY (`id`)
) ENGINE=InnoDB DEFAULT CHARSET=latin1 AUTO_INCREMENT=1 ;

CREATE TABLE `namecoin_blocks` (
  `id` bigint(20) NOT NULL AUTO_INCREMENT,
  `timestamp` int(11) NOT NULL,
  `time` timestamp NOT NULL DEFAULT CURRENT_TIMESTAMP ON UPDATE CURRENT_TIMESTAMP,
  `txid` varchar(64) NOT NULL DEFAULT 'NONE',
  `type` varchar(64) NOT NULL,
  `amount` decimal(16,8) NOT NULL,
  `confirmations` int(11) NOT NULL,
  `blk_num` varchar(64) NOT NULL,
  PRIMARY KEY (`id`)
) ENGINE=InnoDB DEFAULT CHARSET=latin1 AUTO_INCREMENT=1 ;

CREATE TABLE `namecoin_payouts` (
  `id` bigint(20) NOT NULL AUTO_INCREMENT,
  `timestamp` int(11) NOT NULL,
  `time` timestamp NOT NULL DEFAULT CURRENT_TIMESTAMP ON UPDATE CURRENT_TIMESTAMP,
  `address` varchar(48) NOT NULL,
  `amount` decimal(16,8) NOT NULL,
  `txid` varchar(64) NOT NULL DEFAULT 'NONE',
  `paddress` varchar(48) NOT NULL,
  `paid` varchar(36) NOT NULL,
  PRIMARY KEY (`id`)
) ENGINE=InnoDB DEFAULT CHARSET=latin1 AUTO_INCREMENT=1 ;

CREATE TABLE `namecoin_reg` (
  `BTC_address` varchar(36) NOT NULL,
  `NMC_address` varchar(36) NOT NULL,
  PRIMARY KEY (`BTC_address`)
) ENGINE=InnoDB DEFAULT CHARSET=latin1 AUTO_INCREMENT=1 ;

CREATE TABLE `devcoin_blocks` (
  `id` bigint(20) NOT NULL AUTO_INCREMENT,
  `timestamp` int(11) NOT NULL,
  `time` timestamp NOT NULL DEFAULT CURRENT_TIMESTAMP ON UPDATE CURRENT_TIMESTAMP,
  `txid` varchar(64) NOT NULL DEFAULT 'NONE',
  `type` varchar(64) NOT NULL,
  `amount` decimal(16,8) NOT NULL,
  `confirmations` int(11) NOT NULL,
  `blk_num` varchar(64) NOT NULL,
  PRIMARY KEY (`id`)
) ENGINE=InnoDB DEFAULT CHARSET=latin1 AUTO_INCREMENT=1 ;

CREATE TABLE `devcoin_payouts` (
  `id` bigint(20) NOT NULL AUTO_INCREMENT,
  `timestamp` int(11) NOT NULL,
  `time` timestamp NOT NULL DEFAULT CURRENT_TIMESTAMP ON UPDATE CURRENT_TIMESTAMP,
  `address` varchar(48) NOT NULL,
  `amount` decimal(16,8) NOT NULL,
  `txid` varchar(64) NOT NULL DEFAULT 'NONE',
  `paddress` varchar(48) NOT NULL,
  `paid` varchar(36) NOT NULL,
  PRIMARY KEY (`id`)
) ENGINE=InnoDB DEFAULT CHARSET=latin1 AUTO_INCREMENT=1 ;

CREATE TABLE `devcoin_reg` (
  `BTC_address` varchar(36) NOT NULL,
  `NMC_address` varchar(36) NOT NULL,
  PRIMARY KEY (`BTC_address`)
) ENGINE=InnoDB DEFAULT CHARSET=latin1 AUTO_INCREMENT=1 ;

CREATE TABLE `i0coin_blocks` (
  `id` bigint(20) NOT NULL AUTO_INCREMENT,
  `timestamp` int(11) NOT NULL,
  `time` timestamp NOT NULL DEFAULT CURRENT_TIMESTAMP ON UPDATE CURRENT_TIMESTAMP,
  `txid` varchar(64) NOT NULL DEFAULT 'NONE',
  `type` varchar(64) NOT NULL,
  `amount` decimal(16,8) NOT NULL,
  `confirmations` int(11) NOT NULL,
  `blk_num` varchar(64) NOT NULL,
  PRIMARY KEY (`id`)
) ENGINE=InnoDB DEFAULT CHARSET=latin1 AUTO_INCREMENT=1 ;

CREATE TABLE `i0coin_payouts` (
  `id` bigint(20) NOT NULL AUTO_INCREMENT,
  `timestamp` int(11) NOT NULL,
  `time` timestamp NOT NULL DEFAULT CURRENT_TIMESTAMP ON UPDATE CURRENT_TIMESTAMP,
  `address` varchar(48) NOT NULL,
  `amount` decimal(16,8) NOT NULL,
  `txid` varchar(64) NOT NULL DEFAULT 'NONE',
  `paddress` varchar(48) NOT NULL,
  `paid` varchar(36) NOT NULL,
  PRIMARY KEY (`id`)
) ENGINE=InnoDB DEFAULT CHARSET=latin1 AUTO_INCREMENT=1 ;

CREATE TABLE `i0coin_reg` (
  `BTC_address` varchar(36) NOT NULL,
  `NMC_address` varchar(36) NOT NULL,
  PRIMARY KEY (`BTC_address`)
) ENGINE=InnoDB DEFAULT CHARSET=latin1 AUTO_INCREMENT=1 ;

CREATE TABLE `ixcoin_blocks` (
  `id` bigint(20) NOT NULL AUTO_INCREMENT,
  `timestamp` int(11) NOT NULL,
  `time` timestamp NOT NULL DEFAULT CURRENT_TIMESTAMP ON UPDATE CURRENT_TIMESTAMP,
  `txid` varchar(64) NOT NULL DEFAULT 'NONE',
  `type` varchar(64) NOT NULL,
  `amount` decimal(16,8) NOT NULL,
  `confirmations` int(11) NOT NULL,
  `blk_num` varchar(64) NOT NULL,
  PRIMARY KEY (`id`)
) ENGINE=InnoDB DEFAULT CHARSET=latin1 AUTO_INCREMENT=1 ;

CREATE TABLE `ixcoin_payouts` (
  `id` bigint(20) NOT NULL AUTO_INCREMENT,
  `timestamp` int(11) NOT NULL,
  `time` timestamp NOT NULL DEFAULT CURRENT_TIMESTAMP ON UPDATE CURRENT_TIMESTAMP,
  `address` varchar(48) NOT NULL,
  `amount` decimal(16,8) NOT NULL,
  `txid` varchar(64) NOT NULL DEFAULT 'NONE',
  `paddress` varchar(48) NOT NULL,
  `paid` varchar(36) NOT NULL,
  PRIMARY KEY (`id`)
) ENGINE=InnoDB DEFAULT CHARSET=latin1 AUTO_INCREMENT=1 ;

CREATE TABLE `ixcoin_reg` (
  `BTC_address` varchar(36) NOT NULL,
  `NMC_address` varchar(36) NOT NULL,
  PRIMARY KEY (`BTC_address`)
) ENGINE=InnoDB DEFAULT CHARSET=latin1 AUTO_INCREMENT=1 ;

CREATE TABLE `coiledcoin_blocks` (
  `id` bigint(20) NOT NULL AUTO_INCREMENT,
  `timestamp` int(11) NOT NULL,
  `time` timestamp NOT NULL DEFAULT CURRENT_TIMESTAMP ON UPDATE CURRENT_TIMESTAMP,
  `txid` varchar(64) NOT NULL DEFAULT 'NONE',
  `type` varchar(64) NOT NULL,
  `amount` decimal(16,8) NOT NULL,
  `confirmations` int(11) NOT NULL,
  `blk_num` varchar(64) NOT NULL,
  PRIMARY KEY (`id`)
) ENGINE=InnoDB DEFAULT CHARSET=latin1 AUTO_INCREMENT=1 ;

CREATE TABLE `coiledcoin_payouts` (
  `id` bigint(20) NOT NULL AUTO_INCREMENT,
  `timestamp` int(11) NOT NULL,
  `time` timestamp NOT NULL DEFAULT CURRENT_TIMESTAMP ON UPDATE CURRENT_TIMESTAMP,
  `address` varchar(48) NOT NULL,
  `amount` decimal(16,8) NOT NULL,
  `txid` varchar(64) NOT NULL DEFAULT 'NONE',
  `paddress` varchar(48) NOT NULL,
  `paid` varchar(36) NOT NULL,
  PRIMARY KEY (`id`)
) ENGINE=InnoDB DEFAULT CHARSET=latin1 AUTO_INCREMENT=1 ;

CREATE TABLE `coiledcoin_reg` (
  `BTC_address` varchar(36) NOT NULL,
  `NMC_address` varchar(36) NOT NULL,
  PRIMARY KEY (`BTC_address`)
) ENGINE=InnoDB DEFAULT CHARSET=latin1 AUTO_INCREMENT=1 ;

CREATE TABLE `groupcoin_blocks` (
  `id` bigint(20) NOT NULL AUTO_INCREMENT,
  `timestamp` int(11) NOT NULL,
  `time` timestamp NOT NULL DEFAULT CURRENT_TIMESTAMP ON UPDATE CURRENT_TIMESTAMP,
  `txid` varchar(64) NOT NULL DEFAULT 'NONE',
  `type` varchar(64) NOT NULL,
  `amount` decimal(16,8) NOT NULL,
  `confirmations` int(11) NOT NULL,
  `blk_num` varchar(64) NOT NULL,
  PRIMARY KEY (`id`)
) ENGINE=InnoDB DEFAULT CHARSET=latin1 AUTO_INCREMENT=1 ;

CREATE TABLE `groupcoin_payouts` (
  `id` bigint(20) NOT NULL AUTO_INCREMENT,
  `timestamp` int(11) NOT NULL,
  `time` timestamp NOT NULL DEFAULT CURRENT_TIMESTAMP ON UPDATE CURRENT_TIMESTAMP,
  `address` varchar(48) NOT NULL,
  `amount` decimal(16,8) NOT NULL,
  `txid` varchar(64) NOT NULL DEFAULT 'NONE',
  `paddress` varchar(48) NOT NULL,
  `paid` varchar(36) NOT NULL,
  PRIMARY KEY (`id`)
) ENGINE=InnoDB DEFAULT CHARSET=latin1 AUTO_INCREMENT=1 ;

CREATE TABLE `groupcoin_reg` (
  `BTC_address` varchar(36) NOT NULL,
  `NMC_address` varchar(36) NOT NULL,
  PRIMARY KEY (`BTC_address`)
) ENGINE=InnoDB DEFAULT CHARSET=latin1 AUTO_INCREMENT=1 ;

Thanks for the help!
18  Alternate cryptocurrencies / Announcements (Altcoins) / Re: [ANN][NEW][PesetaCoin - PTC] Blonde Returns!! Exchange Listed on: March 07, 2014, 03:41:18 PM
PTC is on AllCrypt ~!!
19  Alternate cryptocurrencies / Announcements (Altcoins) / Re: [ANN][NEW][PesetaCoin - PTC] Blonde Returns!! Exchange Listed on: March 07, 2014, 03:26:03 PM
I would buy, but cryptorush is taking forever to credit my btc.
20  Alternate cryptocurrencies / Announcements (Altcoins) / Re: [ANN][NEW][PesetaCoin - PTC] Blonde Returns!! Exchange Listed on: March 07, 2014, 01:55:55 PM
We have to buy up the amounts on cryptorush.in
Cannot do it on my own.
just 0,7 BTC to 8000 satoshi.

^ this.

Buy PTC on rush, only sell on forums or to individuals. This will prop up the value of the coin.

Also, if someone is willing to sell goods/services for PTC, it increases the value.
Pages: [1] 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 ... 54 »
Sponsored by , a Bitcoin-accepting VPN.
Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!