Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Topics - yago

Pages: [1] 2
Just tried it with a friend and it works great! :)

I'm @yago there ;)

Edit: Warning! This is alpha software!

General Discussion / [Scam] PTS messenger / All4coins
« on: December 31, 2013, 09:49:01 am »
What happened: All4coins sent several PM with a link to a supposed "PTS messenger", but it seems to be a trojan keylogger.
Scammers Profile Link:;u=5056
Reference Link: none
Amount Scammed:  none to me, unknown to others.
Payment Method: none
Proof of Payment: none
PM/Chat Logs:
Hey yago,

i would like to support PTS.
I´m a programmer and was thinking about what could be a nice unique feature for a coin.
Now i have codet a PTS messenger.
It´s a messenger like msn or icq but here u will add people with ur wallet id.
And u can see the btc & PTS price everytime.
Also i´m thinking about a giveaway option like "for every day using messenger = 0.01 PTS or something".
Also i linked ur domain, qt download and other stuff of PTS in the messenger.

PTS Messenger Login:

PTS Messenger Buddys:

PTS Messenger Conversation:


ProtoShare Messenger v1.0.2

I hope u like it if u have some suggestions what i can add or somethink what i have to change let me know.
I´m waiting for ur judgement and suggestions before i will share the messenger in the forum.

Here is your test Account for the messenger because the registration is closed at the moment i´m working on my server.

ID: testid
Password: testaccount

You can add me for testing the chat if u like
My ID: admintest

friendly greetings All4coins
(sry for my bad english :D)

Additional Notes: Tested that exe on virustotal, raised a lot of keylogger flags:

Malwr dynamic analysis:

It tries to connect to, collects information to fingerprint the system and installs itself for autorun at windows startup.

Seems that this guy is trying to steal other alt coins too:

Meta / Username faking via Unicode homoglyphs
« on: December 13, 2013, 09:17:26 pm »
Beware: username faking via Unicode homoglyphs is possible.

Hope that scammers do not exploit that, but just in case...

Read the advisory here:

BitShares PTS / PTS added to
« on: December 01, 2013, 02:17:42 am »
It has bter / cryptsy long time price charts!  :D

Long time data... since Nov 30 2013! (yes, that was yesterday)

Don't trust this donation address, as the message is not signed! Please ask him for a public donation address instead.

El 30/11/13 23:13, Christian Eisenberg escribió:

i am a huge fan on protoshare new things are coming.
unfortunately they are really expensive these days.
of course i have added the trading pairs to cryptocoincharts now. data is calculating. will need some minutes.

a PTS donation to this address would be very fine!!

thank you

On 11/29/2013 08:42 AM, Yago wrote:
> Hi Christian,
> Would be really nice if you add ProtoShares (PTS) to
> Markets:
> Also if you accept PTS donations
> If you do, please tell me and I will promote your site on
> Thank you!

3 domains bought some time ago and now I think that someone on this forum may want them.

  • tradecoin.bit
  • tradecoins.bit
  • wetrade.bit

They have a lot of potential, may be used to run an uncensorable coin trade site! Or to sell later to someone else.

Just 3.27 PTS/each.

If you buy all 3, then is only 3 PTS/each.

Remember to use the newer namecoind v. 3.72, that has the name enforcing bug fixed:
A severe bug was found in the name verification code. It has been fixed as of version Q.3.72
Only trust the fixed version Q.3.72 or higher with names!
See: and

You pay first or escrow on your costs with Lighthouse or favdesu.

If you're going to pay first, you should always check that the seller really own the domain, like this:

Code: [Select]
$ namecoind name_scan "d/tradecoin" 1
        "name" : "d/tradecoin",
        "value" : "Buy this domain user: yago",
        "expires_in" : 36000

$ namecoind name_scan "d/tradecoins" 1
        "name" : "d/tradecoins",
        "value" : "Buy this domain user: yago",
        "expires_in" : 36000

$namecoind name_scan "d/wetrade" 1
        "name" : "d/wetrade",
        "value" : "Buy this domain user: yago",
        "expires_in" : 35999

General Discussion / BTC withdrawal stuck
« on: November 28, 2013, 07:52:22 pm »
I have a problem trying to withdrawal some BTC from bter. Sent an email to them 24 hours ago without response  >:(

That was the email sent to [email protected]:

I made a request for a BTC withdrawal several hours ago. After that,
made another withdrawal and it worked almost instant.

The stuck withdrawal ID is: 39806
Address to send the payment: 12aEGrXxQHMVtqAPbztYbtzfgyGfoov3Gc
Amount: 0.0375
Date: Processing

Maybe they are at a party and dont want to know anything about the support mail?

Marketplace / [WTS] 10 PTS @ 0.02 BTC. TOTAL=0.2 BTC
« on: November 27, 2013, 01:12:15 pm »
WTS 10 PTS @ 0.02 BTC. TOTAL=0.2 BTC

You pay first or escrow on your costs with Lighthouse or favdesu.

Marketplace / [WTB] 10 PTS @ 0.009 BTC. TOTAL=0.09 BTC
« on: November 27, 2013, 01:06:01 pm »
WTB 10 PTS @ 0.009 BTC

10 x 0.009 =  0.09 BTC

You pay first or escrow on your costs with Lighthouse or favdesu.

Meta / Access from tor banned sometimes?
« on: November 26, 2013, 03:19:27 pm »
After using this site from tor for some time, today I got this message:

"This request has been denied for security reasons. If you believe this was in error, please contact support."

I changed my tor exit node (IP) to post this, and seems that now it works.

Marketplace / WTB 10 PTS @ 0.008 (CANCELED)
« on: November 25, 2013, 02:08:48 pm »
WTB 10 PTS @ 0.008.

10 x 0.008 = 0.08 BTC

You pay first or escrow on your costs with Lighthouse or favdesu.

Edit: timeout, canceled

Español (Spanish) / ¿Qué son las ProtoShares?
« on: November 12, 2013, 09:13:59 am »
Traducción no oficial de:

¡Tener ProtoShares es una forma de adquirir futuros BitShares y especular con su valor hoy!

¿Qué es ProtoShares?
Es un tipo de cripto-moneda que te permite capturar una posición en una o más DACs antes incluso de que se implementen. El valor especulativo de una DAC de ProtoShares es una mezcla subjetiva de los 3 pilares que percibe el mercado:

• El valor especulativo de una futura acción de una DAC.
• La probabilidad de que la DAC pueda y sea lanzada.
• La confianza de que ProtoShares se corresponda con una participación en las acciones que sea equitativa en la implementación.

Los desarrolladores usan ProtoShares para reunir capital con el que implementar una nueva idea. Son una nueva forma descentralizada de crowdsourcing que usa una tecnología de cadena de bloques y contratos sociales que son incorruptibles, en lugar de abogados, banqueros y reguladores, para financiar y lanzar una nueva empresa.

Los inversores usan ProtoShares para tener alguna participación desde el principio de una idea que reconocen que tiene potencial. Continúan comerciando con ellas para que se genere un examen público en foros de debate y aumenten las probabilidades de que otros inversores y desarrolladores se involucren en hacer la idea realidad. A medida que el examen público se desarrolla, todo el mundo puede decidir si quiere más o menos acciones.

Los desarrolladores e inversores empiezan todos al mismo nivel para obtener ProtoShares. Ambos pueden empezar a minar y a comerciar con ellas a partir de una fecha anunciada previamente. La única ventaja del desarrollador es creer que su idea tendrá éxito y poder adquirir sus protoshares antes de que el mercado general las demande y suba su valor. La lenta generación de nuevas acciones mantiene la producción en línea con la demanda de tal manera que el precio de la acción pueda reflejar el valor de consenso de las acciones en el momento que el mercado pueda examinar de cerca la idea.

¿Y sobre el tercer pilar?

El tercer pilar en el que se apoya la percepción pública es la confianza de que teniendo una ProtoShare de una DAC se traducirá en una propiedad real de una parte equitativa de las acciones de la DAC objetivo. Es tarea del desarrollador de la DAC convencer al mercado de que esto será así usando cualquier contrato social que el mercado esté dispuesto a aceptar. El Contrato Social General de Invictus Innovations para nuestro ProtoShares es el siguiente

En el momento del lanzamiento, anunciado con anterioridad, Invictus inicializará el bloque
   génesis de la DAC para que correspondan exactamente las salidas no gastadas de su correspondiente
   cadena de bloques ProtoShares.

N.T.: Contrato Social original a continuación:
  At our DAC’s pre-published launch time, Invictus will initialize the DAC’s genesis block
    to precisely match the current unspent outputs of its corresponding ProtoShares blockchain.

Por cada protoshare que tengas en el momento del lanzamiento, tendrás una parte correspondiente en la DAC que podrás acceder usando la misma dirección pública para la cual guardas su clave privada.

Eso es todo. Simple. Fácil de entender.

¿Qué queréis decir con "bien difícil de renegar" en vuestro contrato social?

¿Quién querría abandonar a un universo entero de pioneros informados renegando de sus derechos como accionistas fundadores? En éste negocio, el efecto en red de la cuota de mercado lo es todo. Además, si alguien desarrolla una DAC de código abierto sin cumplir su contrato social con los propietarios de ProtoShares, alguien más simplemente hará un fork del código abierto y cumplirá el contrato. Bingo, ya empezó el negocio! El efecto en red de los pioneros informados hará el resto y la implementación del desarrollador que renegó acabará en el cubo de la basura de la historia.

Not sure why, but got those "force reconnect if possible!" errors.

Found a post by xolokram @ peercointalk that says:

"the typical behaviour for the miner when the connection is lost is to continue mining for 5 minutes (this is when the "force reconnect if possible!" log line appears) and when a thread finds a share during this period, the thread waits until the connection is back again to submit it. unfortunately the triggers are not always working correctly (the current implementation is a bit 'clunky' regarding connection loss) and a thread continues mining forever on the old block. especially when you have unstable connections or partly blocked connections or any behaviour that's far off from (let's say) "normal".

I've just made a simple software watchdog that restarts ptsminer if detects a "force reconnect" error. Just change the folder, pooluser and genproclimit to mine @ beer pool.

Edit: Added proper process killing with Ctrl-C and move old log to ~/ptsminer.log.old

Code: [Select]

#Tips welcome :) PYfnvSc9CRHCebGDtVkSijo6k7pCbpPthX

function launchptsminer {
echo "######## Starting ptsminer... ########"
cd ~/src/ptsminer/src/
./ptsminer -poolport=1337 -poolpassword=0 -pooluser=PYfnvSc9CRHCebGDtVkSijo6k7pCbpPthX -genproclimit=4 > ~/ptsminer.log &

echo "######## Stopping  ########"
ps aux | grep tail | grep ptsminer | awk  '{print "kill "$2}' | sh
killall ptsminer
exit 0
trap control_c SIGINT

mv ~/ptsminer.log ~/ptsminer.log.old 2> /dev/null


tail -f ~/ptsminer.log &

while true
grep "force reconnect" ~/ptsminer.log
if [ $? -eq 0 ]
echo "######## Force reconnect DETECTED ########"
echo "######## Killing ptsminer... ########"
killall ptsminer
echo "######## Wait 5 secs... ########"
sleep 5s
sleep 1s

BitShares PTS / Block generated but no PTS on wallet
« on: November 07, 2013, 11:05:18 am »
Code: [Select]
Hash Target 000fff0000000000000000000000000000000000000000000000000000000000
testHash 00026746b47cbfe482e91205395b81d11efed2137b2819daf93ceccab0528540
Hash Target 000fff0000000000000000000000000000000000000000000000000000000000
Found Hash 00026746b47cbfe482e91205395b81d11efed2137b2819daf93ceccab0528540
hash 00026746b47cbfe482e91205395b81d11efed2137b2819daf93ceccab0528540
hash2 00026746b47cbfe482e91205395b81d11efed2137b2819daf93ceccab0528540
proof-of-work found 
  hash: 00026746b47cbfe482e91205395b81d11efed2137b2819daf93ceccab0528540 
target: 000fff0000000000000000000000000000000000000000000000000000000000
CBlock(hash=00026746b47cbfe482e91205395b81d11efed2137b2819daf93ceccab0528540, ver=2, hashPrevBlock=0000db4
daa0e9b571f4a5f02ced38c5a9b31df35826b0111f6bcfa1526a53909, hashMerkleRoot=61cf09d8d734eea9b17ac181e174c355
d746197612183d9467bf247238dae6cd, nTime=1383763047, nBits=20000fff, nNonce=20, vtx=1, birthdayA=9023686, b
  CTransaction(hash=61cf09d8d734eea9b17ac181e174c355d746197612183d9467bf247238dae6cd, ver=1, vin.size=1, v
out.size=1, nLockTime=0)
    CTxIn(COutPoint(0000000000000000000000000000000000000000000000000000000000000000, 4294967295), coinbas
e 028d0d0102062f503253482f)
    CTxOut(nValue=47.50000000, scriptPubKey=03b3c74cf11fa828f730c198bcbd8c)
  vMerkleTree: 61cf09d8d734eea9b17ac181e174c355d746197612183d9467bf247238dae6cd
generated 47.50
keypool keep 2
AddToWallet 61cf09d8d734eea9b17ac181e174c355d746197612183d9467bf247238dae6cd  new
Committing 2 changed transactions to coin database...
SetBestChain: new best=00026746b47cbfe482e91205395b81d11efed2137b2819daf93ceccab0528540  height=3469  log2_work=23.761072  tx=4174  date=2013-11-06 18:37:27 progress=0.000083
ProcessBlock: ACCEPTED
keypool reserve 4
CreateNewBlock(): total size 1000
Running ProtoSharesMiner with 1 transactions in block (196 bytes)

    "version" : 80500,
    "protocolversion" : 70001,
    "walletversion" : 60000,
    "balance" : 0.00000000,
    "blocks" : 4936,
    "timeoffset" : 0,
    "connections" : 9,
    "proxy" : "",
    "difficulty" : 0.00000382,
    "testnet" : false,
    "keypoololdest" : 1383757981,
    "keypoolsize" : 101,
    "paytxfee" : 0.00000000,
    "errors" : ""

Edit: why?

BitShares PTS / Stale blocks
« on: November 07, 2013, 11:00:47 am »

So, I've 3 machines with aprox. 6.6 HPS total and got 4/4 Stale blocks.

[email protected] ~ $ grep generated ~/.protoshares/debug.log
generated 50.00
ERROR: ProtoSharesMiner : generated block is stale
generated 50.00
ERROR: ProtoSharesMiner : generated block is stale
generated 47.50
ERROR: ProtoSharesMiner : generated block is stale
generated 45.125
ERROR: ProtoSharesMiner : generated block is stale

Still no good blocks  :'(

Maybe I'm doing something wrong?

Pages: [1] 2