🌟 [SIL] 611 (SixEleven) ◥◣ FREE ANONYMOUS DOMAIN NAME SYSTEM ◥◣ 🌟 - page 2.

PatrickMacH

sr. member

Activity: 443

Merit: 251

Quote from: crypto_trader#43xzEXrP on October 05, 2019, 11:36:21 PM

Hi, PatrickMacH.
Can you add supporting for www. domains?
I see https://paperwallet.611.to - is opening good.
Also https://www.paperwallet.611.to - is opening good, too.
But...

https://be.611.to - is opening good.
https://www.be.611.to - Web-page is not available, or another site is opening.

Good hint. Will take care about it.

Quote from: crypto_trader#43xzEXrP on October 05, 2019, 11:36:21 PM

I just tryed to get free SSL certificate here: https://www.sslforfree.com/
And I did verify my domain name, using "Manual Verification".
Then I did upload that file, in "/.well-known/acme-challenge/" folder.
To create "/.well-known/"-folder on windows, I did use the command:

Code:

cmd.exe
cd folderpath
md .well-known

Then, this service return me SSL certificates.
But... Is see this was been registered to www.blahblahblahblahblahblahblah.611.to, not for blahblahblah.611.to
So this seems, like invalid certificate.

P.S.: ZeroSSL also provide the SSL certificates for www.domain.name, not for domain.name

Letsencrypt should work fine.

Take care to register the d/DOMAIN object for both itself and WWW, like i.e.:

Code:

{"ip":"1.2.3.4","map":{"www":{"ip":"1.2.3.4"}}}

crypto_trader#43xzEXrP

full member

Activity: 1589

Merit: 214

Hi, PatrickMacH.
Can you add supporting for www. domains?
I see https://paperwallet.611.to - is opening good.
Also https://www.paperwallet.611.to - is opening good, too.
But...

https://be.611.to - is opening good.
https://www.be.611.to - Web-page is not available, or another site is opening.

I just tryed to get free SSL certificate here: https://www.sslforfree.com/
And I did verify my domain name, using "Manual Verification".
Then I did upload that file, in "/.well-known/acme-challenge/" folder.
To create "/.well-known/"-folder on windows, I did use the command:

Code:

cmd.exe
cd folderpath
md .well-known

Then, this service return me SSL certificates.
But... Is see this was been registered to www.blahblahblahblahblahblahblah.611.to, not for blahblahblah.611.to
So this seems, like invalid certificate.

P.S.: ZeroSSL also provide the SSL certificates for www.domain.name, not for domain.name

PatrickMacH

sr. member

Activity: 443

Merit: 251

Hi Elpaisa,

Quote from: Elpaisa on October 01, 2019, 12:24:57 PM

Now that I have to withdraw my currency exchange coins.
In which wallet can I store them?

In general the use of the official 611 coin wallet is recommended:
https://611project.org/explore/

If you just like to store your assets safely the use the Paperwallet should be considered:
https://paperwallet.611.to

The PaperWallet can also be used to generate Bitcoin and other crypto offline currency wallets.

crypto_trader#43xzEXrP

full member

Activity: 1589

Merit: 214

Quote from: Elpaisa on October 01, 2019, 12:24:57 PM

Now that I have to withdraw my currency exchange coins.
In which wallet can I store them?

You can using piWallet-based web-wallet: https://wallet.611.to/
This no need to download blockchain, and available online.
Also, you can download https://github.com/611project/sixeleven/releases
Generate the address, dumprivkey from this, and send coins there.
In this case, if you will not move your coins and will not pay anything, and just hold this,
you can sign the transaction by privkey at anytime,
and you can do "importprivkey" to another wallet, if this privkey will be saved.
Also, you can just generate your address, then, dumpprivkey, then delete wallet.dat,
and accept your coins to address.
You can see balance on https://be.611.to/address/ADDRESS
and while only you have your privkey, no one cann't spend your coins,
and you can do "importprivkey" for this key at any time.
But... If you will pay for someone or pay for name, then the rest of your coins inside qt-wallet
will be moved to new addresses every time for each transfer,
and in this case you need to do "dumpprivkey" for each address,
because this is saved in "wallet.dat", and this file can be damaged, or data inside can be corrupted. Grin

So if this moving cannt' be disabled, will be better to using that piWallet-based web-wallet, IMHO.

Quote from: PatrickMacH on September 29, 2019, 08:13:41 PM

WOW, thanks for your awesome summary on your debugging experience Cool

Hi, PatrickMacH! You can using preview button, before send your post.

Quote from: PatrickMacH on September 29, 2019, 08:13:41 PM

Did you check the outputs in debug.log?

No, but now I saw this.
I see long logs, in this old debug.log, and I just did search keyword "error" there.
I see some errors:

Code:

...
dbenv.open strLogDir=D:\coins\611\611-qt_win32\data/database strErrorFile=D:\coins\611\611-qt_win32\data/db.log
...
ERROR: CheckProofOfWork() : hash doesn't match nBits
ERROR: CheckProofOfWork() : proof of work failed
ERROR: CBlock::ReadFromDisk() : errors in block header
...
Warning: AddSupportingTransactions() : unsupported transaction
CreateTransactionWithInputTx succeeded:
CTransaction(hash=797007ac08, ver=611, vin.size=2, vout.size=3, nLockTime=0)
    CTxIn(COutPoint(0dadfa6ecf, 1), scriptSig=3046022100b8519a10d50ab7)
    CTxIn(COutPoint(7beec3fae5, 0), scriptSig=3045022100a603368498e2ed)
    CTxOut(nValue=663.63150000, scriptPubKey=04ef2be110d2a9f3ce158c13a0df3d)
    CTxOut(nValue=0.01000000, scriptPubKey=2 642f6e6f6465 edc3b53f3bcbf29)
    CTxOut(error)
...
Warning: AddSupportingTransactions() : unsupported transaction
CreateTransactionWithInputTx succeeded:
CTransaction(hash=1af560e2f8, ver=611, vin.size=1, vout.size=2, nLockTime=0)
    CTxIn(COutPoint(dfcf12d47c, 1), scriptSig=30450220716103aa8c403bdc)
    CTxOut(nValue=0.01000000, scriptPubKey=2 642f6e6f6465 edc3b53f3bcbf29)
    CTxOut(error)
Automatic name_firstupdate created for name d/node (initial, with empty value), created tx: 1af560e2f8a0d7392ef2b4131c95ab3558fabe0112c46d09965133aa1e8cb0bf:
CTransaction(hash=1af560e2f8, ver=611, vin.size=1, vout.size=2, nLockTime=0)
    CTxIn(COutPoint(dfcf12d47c, 1), scriptSig=30450220716103aa8c403bdc)
    CTxOut(nValue=0.01000000, scriptPubKey=2 642f6e6f6465 edc3b53f3bcbf29)
    CTxOut(error)
CommitTransaction:
CTransaction(hash=dfcf12d47c, ver=611, vin.size=1, vout.size=2, nLockTime=0)
    CTxIn(COutPoint(7beec3fae5, 0), scriptSig=30450220080139a5f4543e46)
    CTxOut(nValue=663.56040000, scriptPubKey=0407d3c66822825922820a249e3f6a)
    CTxOut(nValue=0.10110000, scriptPubKey=1 ff311d1b913c82d569fe20dc0526)
...
CreateTransactionWithInputTx: total value = 10110000
CreateTransactionWithInputTx: SelectCoins(0.00), nTotalValue = 0.1011, nWtxinCredit = 0.1011
CreateTransactionWithInputTx: selected 0 tx outs, nValueIn = 0.00
CreateTransactionWithInputTx succeeded:
CTransaction(hash=8117e90750, ver=611, vin.size=1, vout.size=2, nLockTime=0)
    CTxIn(COutPoint(dfcf12d47c, 1), scriptSig=304502205a1877dc70fbc028)
    CTxOut(nValue=0.01000000, scriptPubKey=2 642f6e6f6465 edc3b53f3bcbf29)
    CTxOut(error)
Automatic name_firstupdate created for name d/node, created tx: 8117e9075088dd4fcb9ac7e7f15471775129f923aec2c9922424db0b3e5bcf65:
CTransaction(hash=8117e90750, ver=611, vin.size=1, vout.size=2, nLockTime=0)
    CTxIn(COutPoint(dfcf12d47c, 1), scriptSig=304502205a1877dc70fbc028)
    CTxOut(nValue=0.01000000, scriptPubKey=2 642f6e6f6465 edc3b53f3bcbf29)
    CTxOut(error)
Warning: NameTablePriv::updateEntry: Got CT_UPDATED, but entry is not in model
09/27/19 05:28:57 Flushing wallet.dat
Flushed wallet.dat 74ms
...
Exit program.

Again start...
...
ERROR: AcceptToMemoryPool() : not enough fees
received: tx (10841 bytes)
ERROR: AcceptToMemoryPool() : not enough fees
received: tx (11646 bytes)
ERROR: AcceptToMemoryPool() : not enough fees
received: tx (11267 bytes)
ERROR: AcceptToMemoryPool() : not enough fees
received: tx (11699 bytes)
ERROR: AcceptToMemoryPool() : not enough fees
received: tx (8658 bytes)
ERROR: AcceptToMemoryPool() : not enough fees
received: tx (11653 bytes)
ERROR: AcceptToMemoryPool() : not enough fees
received: tx (8477 bytes)
ERROR: AcceptToMemoryPool() : not enough fees
received: tx (8932 bytes)
ERROR: AcceptToMemoryPool() : not enough fees
received: tx (8481 bytes)
ERROR: AcceptToMemoryPool() : not enough fees
received: tx (8940 bytes)
ERROR: AcceptToMemoryPool() : not enough fees
received: tx (9040 bytes)
ERROR: AcceptToMemoryPool() : not enough fees
received: tx (11446 bytes)
ERROR: AcceptToMemoryPool() : not enough fees
received: tx (10531 bytes)
ERROR: AcceptToMemoryPool() : not enough fees
received: tx (8041 bytes)
ERROR: AcceptToMemoryPool() : not enough fees
received: tx (8945 bytes)
ERROR: AcceptToMemoryPool() : not enough fees
received: tx (11438 bytes)
ERROR: AcceptToMemoryPool() : not enough fees
received: tx (11444 bytes)
ERROR: AcceptToMemoryPool() : not enough fees
received: tx (8611 bytes)
ERROR: AcceptToMemoryPool() : not enough fees
received: tx (8556 bytes)
ERROR: AcceptToMemoryPool() : not enough fees
received: inv (1765 bytes)
  got inventory: tx de2f4aca064ed6d8b0f1  new
askfor tx de2f4aca064ed6d8b0f1   0
  got inventory: tx b8750d3a2969d3829239  new
askfor tx b8750d3a2969d3829239   0
  got inventory: tx 474cb65e4ed2bde7ccc3  new
askfor tx 474cb65e4ed2bde7ccc3   0
  got inventory: tx 52cb79f49be4a3bda41c  new
askfor tx 52cb79f49be4a3bda41c   0
  got inventory: tx 95b12e661e4de3d08bbc  new
askfor tx 95b12e661e4de3d08bbc   0
  got inventory: tx 2566113d34d701261b52  new
askfor tx 2566113d34d701261b52   0
...
Warning: AddSupportingTransactions() : unsupported transaction
CreateTransactionWithInputTx succeeded:
CTransaction(hash=797007ac08, ver=611, vin.size=2, vout.size=3, nLockTime=0)
    CTxIn(COutPoint(0dadfa6ecf, 1), scriptSig=3046022100b8519a10d50ab7)
    CTxIn(COutPoint(7beec3fae5, 0), scriptSig=3045022100a603368498e2ed)
    CTxOut(nValue=663.63150000, scriptPubKey=04ef2be110d2a9f3ce158c13a0df3d)
    CTxOut(nValue=0.01000000, scriptPubKey=2 642f6e6f6465 edc3b53f3bcbf29)
    CTxOut(error)
...
CreateTransactionWithInputTx: total value = 10110000
CreateTransactionWithInputTx: SelectCoins(0.00), nTotalValue = 0.1011, nWtxinCredit = 0.1011
CreateTransactionWithInputTx: selected 0 tx outs, nValueIn = 0.00
Warning: AddSupportingTransactions() : unsupported transaction
CreateTransactionWithInputTx succeeded:
CTransaction(hash=1af560e2f8, ver=611, vin.size=1, vout.size=2, nLockTime=0)
    CTxIn(COutPoint(dfcf12d47c, 1), scriptSig=30450220716103aa8c403bdc)
    CTxOut(nValue=0.01000000, scriptPubKey=2 642f6e6f6465 edc3b53f3bcbf29)
    CTxOut(error)
Automatic name_firstupdate created for name d/node (initial, with empty value), created tx: 1af560e2f8a0d7392ef2b4131c95ab3558fabe0112c46d09965133aa1e8cb0bf:
CTransaction(hash=1af560e2f8, ver=611, vin.size=1, vout.size=2, nLockTime=0)
    CTxIn(COutPoint(dfcf12d47c, 1), scriptSig=30450220716103aa8c403bdc)
    CTxOut(nValue=0.01000000, scriptPubKey=2 642f6e6f6465 edc3b53f3bcbf29)
    CTxOut(error)
CommitTransaction:
CTransaction(hash=dfcf12d47c, ver=611, vin.size=1, vout.size=2, nLockTime=0)
    CTxIn(COutPoint(7beec3fae5, 0), scriptSig=30450220080139a5f4543e46)
    CTxOut(nValue=663.56040000, scriptPubKey=0407d3c66822825922820a249e3f6a)
    CTxOut(nValue=0.10110000, scriptPubKey=1 ff311d1b913c82d569fe20dc0526)
keypool keep 3
...

Another copy of old debug.log have lesser errors, only few:

Code:

...
ERROR: CheckProofOfWork() : hash doesn't match nBits
ERROR: CheckProofOfWork() : proof of work failed
ERROR: CBlock::ReadFromDisk() : errors in block header
...
ERROR: ConnectInputs() : 5bcac3cc57 prev tx already spent
ERROR: AcceptToMemoryPool() : ConnectInputs failed 5bcac3cc57
...
ERROR: ConnectInputs() : 5bcac3cc57 prev tx already spent
ERROR: AcceptToMemoryPool() : ConnectInputs failed 5bcac3cc57
...
This is long debug.log, but there is no any more errors.

Quote from: PatrickMacH on September 29, 2019, 08:13:41 PM

Did you run 611d with the "-rescan" option?

No, because after importing privkeys into the new wallet.dat,
this was been rescanned automatically,
and just need to wait some time to update balance, after privkey imported.
But sometimes program was been closed, and also, I saw the some error of importing the key, in console.

Now I did just restart 611-qr.exe with -rescan options, and old wallet.dat.
Process:

I did backup my files:
1. log.lock
2. addr.dat
3. db.log
4. wallet.dat
5. nameindex.dat
rename debug.log to debug1.log
and new my wallet.dat to good_wallet.dat.
Then I did just copy old wallet.dat to "data"-folder, and...

Code:

Try to run -rescan with synchronized blockchain, old wallet.dat and debug.log:

folder_where_611-qt.exe>611-qt.exe -datadir="data" -rescan
Long time loading...
Done.
But, I see old balance, and old unconfirmed transactions.
So, This was been updated good, after "-rescan".
Exit from the wallet.

See debug.log.
There is many info, but I did find keyword "error":
________________________
dbenv.open strLogDir=D:\coins\611\611-qt_win32\data/database strErrorFile=D:\coins\611\611-qt_win32\data/db.log
...
LoadBlockIndex(): hashBestChain=0000000000000044ce97  height=369350
 block index           82244ms
Loading wallet...
nFileVersion = 61100
 wallet                  119ms
Rescanning last 369350 blocks (from block 0)...
ERROR: CheckProofOfWork() : hash doesn't match nBits
ERROR: CheckProofOfWork() : proof of work failed
ERROR: CBlock::ReadFromDisk() : errors in block header
...
ERROR: ConnectInputs() : 5bcac3cc57 prev tx already spent
ERROR: AcceptToMemoryPool() : ConnectInputs failed 5bcac3cc57
...
And... No any more message with errors, there.

After this, I did rename debug.log to debug2.log, wallet.dat to old_wallet.dat, and good_wallet.dat to wallet.dat
Try to run -rescan with synchronized blockchain, my currnet wallet.dat and new debug.log:

Code:

folder_where_611-qt.exe>611-qt.exe -datadir="data" -rescan
...
new debug.log was been generated.
long time loading...
Done...
All transactions are confirmed. Actual balance I see.
Exit from wallet.

Try to search keyword error in new debug.log:

Code:

dbenv.open strLogDir=D:\coins\611\611-qt_win32\data/database strErrorFile=D:\coins\611\611-qt_win32\data/db.log
ERROR: CheckProofOfWork() : hash doesn't match nBits
ERROR: CheckProofOfWork() : proof of work failed
ERROR: CBlock::ReadFromDisk() : errors in block header

That's all...

Maybe this all info can help you to find the reason of this errors, fix this, and repair something, maybe not, but I hope it. Grin

Quote from: PatrickMacH on September 29, 2019, 08:13:41 PM

Ack: "add dumpwallet and importwallet" should be considered to be added with the upcoming releases.
Meanwhile you can have a look at pyWallet for these kind of tasks.

Ok.

Quote from: PatrickMacH on September 29, 2019, 08:13:41 PM

Don't worry. You have to rescan the blockchain to add your balance using the "-rescan" option on 611d startup.

Ok. I already did run this, and I see... Result you can see in this post...

Quote from: PatrickMacH on September 29, 2019, 08:13:41 PM

Confirmed. I did try to send the raw transaction today and failed with the error that it has already been processed.

Maybe, someone another did send this, as RAW-transaction, and then this was been broadcasted.

Quote from: PatrickMacH on September 29, 2019, 08:13:41 PM

Quote from: crypto_trader#43xzEXrP on September 27, 2019, 01:06:45 AM

Therefore, will be better to you add the option to broadcast signed RAW-transaction, as API method, here: https://be.611.to/q

Ok: it's on the TODO

Ok.

P.S.: I'm using win64 version in "611-qt_win32" folder.
win32 version just was been renamed to old_611-qt.exe, and this was lagging too.
I did start win32 version with Roaming folder, but win64 with "data"-folder, as portable wallet.

Elpaisa

newbie

Activity: 12

Merit: 0

Now that I have to withdraw my currency exchange coins.
In which wallet can I store them?

PatrickMacH

sr. member

Activity: 443

Merit: 251

Quote from: PatrickMacH on September 26, 2019, 11:25:45 PM

________

NEW EXCHANGE: BISQ

Bisq an open-source peer-to-peer application that allows you to buy and sell cryptocurrencies with no registration required.
Bisq supports trading 611 (SixEleven) as an Altcoin: SixEleven ... SIL

What's new with Bisq
Starting with Bisq version 1.1.6, full support for 611 (SixEleven) Altcoin trade pairs has been added to Bisq.

Security
Bisq is as anonymous as it can get. All trades are as anonymous as their payment method is, in Bisq.

Altcoin trades, like 611 (SixEleven) coin, are very anonymous, since you only need to provide your altcoin address for trading in Bisq.
Optional fiat trades need to specify your name and bank account when creating a local Bisq account
Optional face to face trades are risky. Please take appropriate measures to ensure your security trading crypto currencies face to face using Bisq.

Documentation
Bisq has an excellent online documentation:

https://docs.bisq.network/

Please join this thread, if you need any assistance or help to trade 611 (SixEleven) coin using Bisq.

Download
Bisq peer-to-peer crypto currency exchange application can be downloaded in source and binary on Github:
https://github.com/bisq-network/bisq/releases

611 (SixEleven) coin is available in source and binary download on Github:
https://github.com/611project/sixeleven/releases
There you can download the latest precompiled 611 wallet for Windows, Mac OS X and Linux:

Security
Bisq uses strong encryption and peer-to-peer communication using the Tor network to ensure your privacy and security.
611 (SixEleven) coin uses strong encryption, to keep your data secure.

It's awesome using SIL [coins]
Setup your own domains to support for your projects, to make remote access simple, secure and easy. Use SIL [coins] to store and share information anonymously and securely with anyone on the Internet.
Of course you are welcome to trade and invest 611 (SixEleven) [SIL coin].

Does anyone need a hint or Youtube video how to activate SixEleven (SIL) trading with Bisq?

PatrickMacH

sr. member

Activity: 443

Merit: 251

WOW, thanks for your awesome summary on your debugging experience Cool

Quote from: crypto_trader#43xzEXrP on September 27, 2019, 01:06:45 AM

Quote from: PatrickMacH on September 26, 2019, 10:59:16 PM

Had a similar issue a few month ago trying to renew a domain name with expiration > 10k blocks. A specific check function caused other clients to block this renew requests for quite some time (until client restart) but finally it did renew without any issues at a later date.

You are welcome to share your raw transaction or send me a priv. msg for debugging.

See my way...

I just did start my wallet, but I see the message inside:

Quote

WARNING: Displayed transactions may not be correct! You may need to upgrade, or other nodes may need to upgrade.

Hm... Ok... Maybe something with blockchain?
Wanted resynchronize wallet. Just deleted all files with old blockchain, and started the wallet again...
Synchronization was been stopped at block 171.
The same problem...

Quote

WARNING: Displayed transactions may not be correct! You may need to upgrade, or other nodes may need to upgrade.

Ok... Go to github, download latest wallet for windows x32 and x64.
Start...
Synchronization was been stopped at block 171...
Again restart... Again, and again...
Finally! Synchronization is processing now... Why? I don't know...

Did you check the outputs in debug.log?

Quote from: crypto_trader#43xzEXrP on September 27, 2019, 01:06:45 AM

Ok, will wait the end of sync... After full synchonization, I see incorrect transactions in wallet...
This was been updated not correctly...
I just tried to spend coins, but this says about coins already spent, and no any coins on that unspent output...
Ok... Maybe... Need... To... Delete wallet.dat, and start with new one?..

Did you run 611d with the "-rescan" option?

Quote from: crypto_trader#43xzEXrP on September 27, 2019, 01:06:45 AM

But, no... Need to just dump private keys at first...
Ok! Go to console... Wanted to dumpwallet.

Code:

dumpwallet "file_path/filename.extension"

But...

Quote

Method not found (-32601)

Ok... So you don't have dumpwallet option, to save all privkeys in human-readable file, like this have ReddByteCoin for example

Ack: "add dumpwallet and importwallet" should be considered to be added with the upcoming releases.
Meanwhile you can have a look at pyWallet for these kind of tasks.

Quote from: crypto_trader#43xzEXrP on September 27, 2019, 01:06:45 AM

Therefore, will be better to you add the option to broadcast signed RAW-transaction, as API method, here: https://be.611.to/q

Ok: it's on the TODO

crypto_trader#43xzEXrP

full member

Activity: 1589

Merit: 214

Quote from: PatrickMacH on September 26, 2019, 10:59:16 PM

Had a similar issue a few month ago trying to renew a domain name with expiration > 10k blocks. A specific check function caused other clients to block this renew requests for quite some time (until client restart) but finally it did renew without any issues at a later date.

You are welcome to share your raw transaction or send me a priv. msg for debugging.

See my way...

I just did start my wallet, but I see the message inside:

Quote

WARNING: Displayed transactions may not be correct! You may need to upgrade, or other nodes may need to upgrade.

Hm... Ok... Maybe something with blockchain?
Wanted resynchronize wallet. Just deleted all files with old blockchain, and started the wallet again...
Synchronization was been stopped at block 171.
The same problem...

Quote

WARNING: Displayed transactions may not be correct! You may need to upgrade, or other nodes may need to upgrade.

Ok... Go to github, download latest wallet for windows x32 and x64.
Start...
Synchronization was been stopped at block 171...
Again restart... Again, and again...
Finally! Synchronization is processing now... Why? I don't know...
Ok, will wait the end of sync... After full synchonization, I see incorrect transactions in wallet...
This was been updated not correctly...
I just tried to spend coins, but this says about coins already spent, and no any coins on that unspent output...
Ok... Maybe... Need... To... Delete wallet.dat, and start with new one?..
But, no... Need to just dump private keys at first...
Ok! Go to console... Wanted to dumpwallet.

Code:

dumpwallet "file_path/filename.extension"

But...

Quote

Method not found (-32601)

Ok... So you don't have dumpwallet option, to save all privkeys in human-readable file, like this have ReddByteCoin for example
Then... Go to list of addresses for receive... Copy this... Then...

Code:

dumpprivkey address1
-> privkey1
dumpprivkey address2
-> privkey2
etc...

Then just add this to .txt-file.
And I think... Maybe... I can to delete this wallet.dat...
But... Stop. Just rename this.
Restart 611-qt.exe...
I see new wallet.dat created.

Then...

Code:

importprivkey privkey1
-> ok
importprivkey privkey2
-> ok
...

But... balance is ZERO.

Where is my coins?..
Just go to block-explorer... And see the chain of transactions...
I see this coins ON ANOTHER ADDRESSES.
OMG. This was been stoled?
Maybe no...
Rename old wallet.dat back.
Restart 611-qt.exe and go to console...

Code:

dumpprivkey address1_with_coins
-> privkey_with_coins_1
dumpprivkey address2_with_coins
-> privkey_with_coins_2

Huh...

Rename wallet.dat to old_wallet.dat... Delete that generated wallet.dat, with empty addresses.
Restart 611-qt.exe. See new wallet.dat was been generated. Full blockchain synchronized. Zero balance. Wallet is ready.
Then go to console.

Code:

importprivkey privkey_with_coins_1
->OK
importprivkey privkey_with_coins_2
->OK

See my coins in the wallet. See only incoming transactions, because this is new wallet...
Then... Just want to register the name...
Do it... See another address generated as owner of this domain name. Maybe coins will go there?.. Hm...
Configure domain name, and send transaction.
Finally, I see my transaction... Just need to wait confirmations...
But... I see blockchain size is growing, synchronization is processed, but no one miner cann't include my transaction...
Maybe, this is not in rawmempool?
Go to console.

Code:

getrawmempool

And I see my transaction there...
Hm... What happened?
Transaction hash is dfcf12d47c01f6ced41aeec6ee618239c78f0044cc4e964d6a4e1eb0e6675813

Code:

getrawtransaction dfcf12d47c01f6ced41aeec6ee618239c78f0044cc4e964d6a4e1eb0e6675813

63020000015eb4433b954a20a4dff43f3797d7afedcb804feef4ef8c30f3b1dde5fac3ee7b00000000494830450220080139a5f4543e461bfcb2e088869d26a62c03892f32c32643ccc92ccd10fe28022100b64115e8768b5e67d0969d0a8eeb2a0d72f6d9b497b2b1f8765bb62f91852d7201ffffffff0240d120730f00000043410407d3c66822825922820a249e3f6ae811729f384c0a49f7954ee593f8ca6ae2580f01b813fe947c19928716e02f196df9f610b662f8226b3f04fd8aec063fce9eac30449a0000000000305114ff311d1b913c82d569fe20dc05263b67efaf45506d76a9144f26af2be9ab955bacc6895b4c2f0e1a6209676c88ac00000000

Code:

signrawtransaction 63020000015eb4433b954a20a4dff43f3797d7afedcb804feef4ef8c30f3b1dde5fac3ee7b00000000494830450220080139a5f4543e461bfcb2e088869d26a62c03892f32c32643ccc92ccd10fe28022100b64115e8768b5e67d0969d0a8eeb2a0d72f6d9b497b2b1f8765bb62f91852d7201ffffffff0240d120730f00000043410407d3c66822825922820a249e3f6ae811729f384c0a49f7954ee593f8ca6ae2580f01b813fe947c19928716e02f196df9f610b662f8226b3f04fd8aec063fce9eac30449a0000000000305114ff311d1b913c82d569fe20dc05263b67efaf45506d76a9144f26af2be9ab955bacc6895b4c2f0e1a6209676c88ac00000000

{
"hex" : "63020000015eb4433b954a20a4dff43f3797d7afedcb804feef4ef8c30f3b1dde5fac3ee7b0000000048473044022011fc66657d4ce857524afc1812ad907dc4536fc07e484b3449255057643527cc022016d7e7346a28b29c512ffd0df3342d2294d73089d4a792d1f5ba7866abb5bfdf01ffffffff0240d120730f00000043410407d3c66822825922820a249e3f6ae811729f384c0a49f7954ee593f8ca6ae2580f01b813fe947c19928716e02f196df9f610b662f8226b3f04fd8aec063fce9eac30449a0000000000305114ff311d1b913c82d569fe20dc05263b67efaf45506d76a9144f26af2be9ab955bacc6895b4c2f0e1a6209676c88ac00000000",
"complete" : true
}

Code:

sendrawtransaction 63020000015eb4433b954a20a4dff43f3797d7afedcb804feef4ef8c30f3b1dde5fac3ee7b00000000494830450220080139a5f4543e461bfcb2e088869d26a62c03892f32c32643ccc92ccd10fe28022100b64115e8768b5e67d0969d0a8eeb2a0d72f6d9b497b2b1f8765bb62f91852d7201ffffffff0240d120730f00000043410407d3c66822825922820a249e3f6ae811729f384c0a49f7954ee593f8ca6ae2580f01b813fe947c19928716e02f196df9f610b662f8226b3f04fd8aec063fce9eac30449a0000000000305114ff311d1b913c82d569fe20dc05263b67efaf45506d76a9144f26af2be9ab955bacc6895b4c2f0e1a6209676c88ac00000000

dfcf12d47c01f6ced41aeec6ee618239c78f0044cc4e964d6a4e1eb0e6675813

And... No any result...

Based on the foregoing, a number of important issues are brewing:

Can you broadcast this my signed RAW-transaction in the miners, from your working wallet, using this hexadecimal value?

Do you see this transaction in "getrawmempool" now?

Can you make the service to broadcast the signed raw-transactions online,
service, like this: https://www.blockchain.com/ru/btc/pushtx ?

Can you make "dumpwallet" option, to save ALL privkeys as human-readable file,
like in ReddByteCoin source-code?

Can you add EACH generated address in the list of address for receive coins, to dump privkey from this?

Can I disable randomly generation of the addresses, and use just one address for each operation?

Can I using my address as address of owner the domain, or set it,
because this is generated randomly, and changed after each operation,
and after wallet is generate this address, this address is available just for copy this, not to change this,
and coins are moved from address to address every time.
If wallet.dat will be damaged, or data will be corrupted, knowledge of my own privkey will not give nothing for me.

Can you make redirect to https://be.611.to/ from http://be.611.to/ within 3 seconds, with ability to cancel this redirect?
Just because transferring addresses and balances as open text over http is not secure, while working the sniffers of traffic.

Do you have online on your block-explorer, the list of unconfirmed transactions?

What version of 611-qt.exe is very-very stable?

Why sometimes, new 611-qt.exe just closing, without any warnings, after enter the command in console? Is there any log-file?

That's all questions from me, right now...

UPD: My transaction was been broadcasted by someone, and confirmed.
After this, I did open my wallet, and I see two more transaction was been generated.
This transactions have 0.00 amount, and this is "name_firstupdate", and "network fee".
Then, those two transactions was been sucessfully broadcasted from my wallet,
I saw it in "getrawmempool", and this already confirmed, now, and was been included immediately in the next block, generated by miners.
Therefore, will be better to you add the option to broadcast signed RAW-transaction, as API method, here: https://be.611.to/q

PatrickMacH

sr. member

Activity: 443

Merit: 251

________

NEW EXCHANGE: BISQ

Bisq an open-source peer-to-peer application that allows you to buy and sell cryptocurrencies with no registration required.
Bisq supports trading 611 (SixEleven) as an Altcoin: SixEleven ... SIL

What's new with Bisq
Starting with Bisq version 1.1.6, full support for 611 (SixEleven) Altcoin trade pairs has been added to Bisq.

Security
Bisq is as anonymous as it can get. All trades are as anonymous as their payment method is, in Bisq.

Altcoin trades, like 611 (SixEleven) coin, are very anonymous, since you only need to provide your altcoin address for trading in Bisq.
Optional fiat trades need to specify your name and bank account when creating a local Bisq account
Optional face to face trades are risky. Please take appropriate measures to ensure your security trading crypto currencies face to face using Bisq.

Documentation
Bisq has an excellent online documentation:

https://docs.bisq.network/

Please join this thread, if you need any assistance or help to trade 611 (SixEleven) coin using Bisq.

Download
Bisq peer-to-peer crypto currency exchange application can be downloaded in source and binary on Github:
https://github.com/bisq-network/bisq/releases

611 (SixEleven) coin is available in source and binary download on Github:
https://github.com/611project/sixeleven/releases
There you can download the latest precompiled 611 wallet for Windows, Mac OS X and Linux:

Security
Bisq uses strong encryption and peer-to-peer communication using the Tor network to ensure your privacy and security.
611 (SixEleven) coin uses strong encryption, to keep your data secure.

It's awesome using SIL [coins]
Setup your own domains to support for your projects, to make remote access simple, secure and easy. Use SIL [coins] to store and share information anonymously and securely with anyone on the Internet.
Of course you are welcome to trade and invest 611 (SixEleven) [SIL coin].

PatrickMacH

sr. member

Activity: 443

Merit: 251

Quote from: crypto_trader#43xzEXrP on September 22, 2019, 03:14:00 PM

My transaction is unconfirmed long time.
I see my transaction hash as result the command

Code:

getrawmempool

,
but this is not included into new generated blocks, and I see this blocks is still is generating.
Do you have any service, like this https://www.blockchain.com/ru/btc/pushtx
to broadcast raw-transaction into the mining-pools,
to miners, to confirm this transaction, and include this in the some block?

I already did try

Code:

getrawtransaction tx_hash

+

Code:

sendrawtransaction HEX_of_RAW_transaction

But... No any result...

I just want to renew my domain name, or I'll just using the long domain names from DDNS-services.

Had a similar issue a few month ago trying to renew a domain name with expiration > 10k blocks. A specific check function caused other clients to block this renew requests for quite some time (until client restart) but finally it did renew without any issues at a later date.

You are welcome to share your raw transaction or send me a priv. msg for debugging.

PatrickMacH

sr. member

Activity: 443

Merit: 251

Quote from: NoobKid220 on September 22, 2019, 09:36:24 PM

I'm having problems getting my wallet to work for some reason??? Did other people have this problem when they first downloaded the wallet???

Should be no problems using any up-to-date wallet version.
What wallet version and OS are you using?
Did you already try to delete the 611 locale path containing the blockchain information and retry the initial synchronization?

PatrickMacH

sr. member

Activity: 443

Merit: 251

Quote from: NoobKid220 on September 22, 2019, 09:33:43 PM

This looks interesting. Is it still tradeable on these exchanges that are listed???

Yes.

Quote from: Elpaisa on August 20, 2019, 07:56:45 PM

for when the new exchange you say?

Additionally Bisq peer-to-peer crypto currency exchange has added support for 611 coin trade pairs, now:

Get started with Bisq ... an open-source peer-to-peer application that allows you to buy and sell cryptocurrencies with no registration required
611/BTC [SIL/BTC] BTC Market on Bisq

Have fun!

NoobKid220

newbie

Activity: 46

Merit: 0

I'm having problems getting my wallet to work for some reason??? Did other people have this problem when they first downloaded the wallet???

NoobKid220

newbie

Activity: 46

Merit: 0

This looks interesting. Is it still tradeable on these exchanges that are listed???

crypto_trader#43xzEXrP

full member

Activity: 1589

Merit: 214

My transaction is unconfirmed long time.
I see my transaction hash as result the command

Code:

getrawmempool

,
but this is not included into new generated blocks, and I see this blocks is still is generating.
Do you have any service, like this https://www.blockchain.com/ru/btc/pushtx
to broadcast raw-transaction into the mining-pools,
to miners, to confirm this transaction, and include this in the some block?

I already did try

Code:

getrawtransaction tx_hash

+

Code:

sendrawtransaction HEX_of_RAW_transaction

But... No any result...

I just want to renew my domain name, or I'll just using the long domain names from DDNS-services.

PatrickMacH

sr. member

Activity: 443

Merit: 251

Quote from: Elpaisa on August 20, 2019, 07:56:45 PM

for when the new exchange you say?

Please be patient. Details are released as soon as the new trade pairs are trade-able.

Elpaisa

newbie

Activity: 12

Merit: 0

for when the new exchange you say?

PatrickMacH

sr. member

Activity: 443

Merit: 251

Quote from: Elpaisa on July 31, 2019, 10:26:05 AM

Is this project abandoned?

No, this project is still active and active.

NEWS Awesome new exchange for 611 trade pairs ahead

Elpaisa

newbie

Activity: 12

Merit: 0

Is this project abandoned?

PatrickMacH

sr. member

Activity: 443

Merit: 251

Shame on any exchange refusing listing of 611 SixEleven coin because of fake news and math.

611 (SixEleven) coin is a solid stable open source project, running since 2015.
Block mining rewards are prove of work since block #1.
All other technical data are shared common like other open-source projects.

To date 611 (SixEleven) coin is the only blockchain offering blockchain to data interaction worldwide to any Internet-connected device supporting DNS (domain name service) queries. That's unique and useful for many projects and tasks.

Thanks to stable community support 611 (SixEleven) is running rock stable and incredibly fast at any location worldwide using anycast technology for the DNS part.

Join development and/or fork the project if you know how to make things better.
Have fun and enjoy it as you like.

Topic: 🌟 [SIL] 611 (SixEleven) ◥◣ FREE ANONYMOUS DOMAIN NAME SYSTEM ◥◣ 🌟 - page 2. (Read 79980 times)