Bitcoin Forum
January 28, 2020, 05:19:21 PM *
News: Latest Bitcoin Core release: 0.19.0.1 [Torrent]
 
   Home   Help Search Login Register More  
Pages: « 1 ... 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175 176 177 178 179 180 181 182 183 184 185 186 [187] 188 189 190 191 192 193 194 195 196 197 198 199 200 201 202 203 204 205 206 207 208 209 210 211 212 213 214 215 216 217 218 219 220 221 222 223 224 225 226 227 228 229 230 231 232 233 234 235 236 237 ... 307 »
  Print  
Author Topic: [PoS+PoW] eXocoin [EXO]-gen 2.0- dev. from scratch! Give-Away | Open Beta  (Read 415101 times)
willowfoot
Sr. Member
****
Offline Offline

Activity: 332
Merit: 252



View Profile
June 15, 2014, 02:30:16 AM
 #3721

I vote Exocoin developer as Qora's marketing leader.

So far he has made Qora look really good. lol


too bad no one is buying Qora as the price keeps going down ... lol

1580231961
Hero Member
*
Offline Offline

Posts: 1580231961

View Profile Personal Message (Offline)

Ignore
1580231961
Reply with quote  #2

1580231961
Report to moderator
1580231961
Hero Member
*
Offline Offline

Posts: 1580231961

View Profile Personal Message (Offline)

Ignore
1580231961
Reply with quote  #2

1580231961
Report to moderator
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction. Advertise here.
a447513372
Sr. Member
****
Offline Offline

Activity: 336
Merit: 250

DLISK - Next Generation Coin


View Profile
June 15, 2014, 03:10:46 AM
 #3722

launch: after final open beta test (that will be after release of v0.6, check download area for more information)
now also have some problem ...

▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄
▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄
           ▄▄▄▄█████████▄▄▄
       ▄▄█████▀▀▀▀▀▀▀▀▀▀▀█████▄▄
     ▄████▀ ▄▄▄▀▀▀▀▀▀▀▀▀▄▄ ▀▀████▄
   ▄███▀ ▄▄▀▀      ████  ▀▀▄▄ ▀▀███▄
  ████ ▄███████████████      ▀█  ████
 ███▀ ▄██████████████████      █  ▀███
▄███            ████ ████      ▀█ ███▄
███ ▄█           ████  ████      █▄ ███
███            ████   ████       █ ███
███ ▀█          ████  ████       █▀ ███
▀▀▀▀           █████████       ▄█ ███▀
 ██████████████████████▄▄▄▄▄▄▄▄█▀ ▄███
  ██████████████████████████████████
    ▄▄▄▄  ▀▄▄       ▀▀▀▀▀▀▀█▀▀▀████▀
     ▀████▄ ▀▀▀▀▄▄▄▄▄▄▄▀▀▀▀ ▄████▀
       ▀▀██████▄▄▄▄▄▄▄▄▄██████▀▀
           ▀▀▀▀█████████▀▀▀▀


                ████                ▄████
    ████████████████                ████   ▄▄███████████████          ▄█████▀
   ██████████████████               ██▀▀ ██████████████████        ▄█████▀
             ▀████████             ███ ████▀                    ▄█████▀
             ▄█████████            ██▀ ███▀                  ▄█████▀
             ████ ▀████           ███ ████▄               ▄█████▀
             ████  ████           ███▄ ██████████████▀ ▄█████▀
            ████  ▄████           ████  ▀████████████▄ ▀█████▄
            ████ ▄████           ████               ▀██▄  █████▄
            ████████▀            ████               ▄████   █████▄
           ███████▀            ███▀              ▄█████▀     █████▄
 ██████████████████████████████ ███ ▄█████████████████▀         █████▄
█████████████▀▀▀██████████████ ▄██ ▄████████████████▀             █████▄

▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄
▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄
Fern
Sr. Member
****
Offline Offline

Activity: 247
Merit: 250



View Profile
June 15, 2014, 05:24:11 AM
 #3723

My console repeatedly has GET TIME REQUEST issues. Hope it helps.

Hang in there, GUI is very intuitive.
gao_fu_shuai
Member
**
Offline Offline

Activity: 74
Merit: 10


View Profile
June 15, 2014, 06:51:35 AM
 #3724

I vote Exocoin developer as Qora's marketing leader.
So far he has made Qora look really good. lol
too bad no one is buying Qora as the price keeps going down ... lol
I know you are missed the qora's ipo ... lol

gao_fu_shuai
Member
**
Offline Offline

Activity: 74
Merit: 10


View Profile
June 15, 2014, 08:30:40 AM
 #3725

I invested for a product of quality.

I couldn't care less if you need another month , Exo dev, take your time and aim for a well shaped code.

Good luck with the work AND with the (unjustified in my opinion, but I respect and understand why some are impatient now) difficult pressure the community will put onto you.

Regards,

A lambda first round IPO
Great,we need to keep supporting dev,complain is stupid.

Sanglotslongs
Sr. Member
****
Offline Offline

Activity: 392
Merit: 250


View Profile
June 15, 2014, 10:26:57 AM
 #3726

Great wallet !

New logo.
Fix blockchain issue.

And all will be fine Smiley


 
 
           ▄████▄
         ▄████████▄
       ▄████████████▄
     ▄████████████████▄
    ████████████████████      ▄█▄                 ▄███▄                 ▄███▄                 ▄████████████████▀   ▄██████████

  ▄▄▄▀█████▀▄▄▄▄▀█████▀▄▄▄     ▀██▄             ▄██▀ ▀██▄             ▄██▀ ▀██▄             ▄██▀                   ██
▄█████▄▀▀▀▄██████▄▀▀▀▄█████▄     ▀██▄         ▄██▀     ▀██▄         ▄██▀     ▀██▄         ▄██▀        ▄█▄          ▀██████████████▄
████████████████████████████       ▀██▄     ▄██▀         ▀██▄     ▄██▀         ▀██▄     ▄██▀          ▀█▀                        ██
 ▀████████████████████████▀          ▀██▄ ▄██▀             ▀██▄ ▄██▀     ▄█▄     ▀██▄ ▄██▀                                       ██
   ▀████████████████████▀              ▀███▀                 ▀███▀       ▀█▀       ▀███▀      ▄███████████████████████████████████▀
     ▀████████████████▀
       ▀████████████▀
         ▀████████▀
           ▀████▀
║║


║║
.
.

║║
██
║║
.
.

║║
██
║║
.
║║


║║
yambad
Full Member
***
Offline Offline

Activity: 120
Merit: 100


View Profile
June 15, 2014, 03:51:13 PM
 #3727

Great wallet !

New logo.
Fix blockchain issue.

And all will be fine Smiley
A wonder. Just a small thing, the such of blockchain what does not. Tongue
provenceday
Legendary
*
Offline Offline

Activity: 1148
Merit: 1000



View Profile
June 15, 2014, 04:04:06 PM
 #3728

Launched?
rriky92
Sr. Member
****
Offline Offline

Activity: 294
Merit: 250



View Profile WWW
June 15, 2014, 06:10:33 PM
 #3729

Launched?

Not yet, i think there is a issue with blockchain
grex
Full Member
***
Offline Offline

Activity: 179
Merit: 100


View Profile
June 15, 2014, 06:28:35 PM
 #3730

I invested for a product of quality.

I couldn't care less if you need another month , Exo dev, take your time and aim for a well shaped code.

Good luck with the work AND with the (unjustified in my opinion, but I respect and understand why some are impatient now) difficult pressure the community will put onto you.

Regards,

A lambda first round IPO

+1
BitzMD
Sr. Member
****
Offline Offline

Activity: 418
Merit: 250



View Profile
June 15, 2014, 06:29:40 PM
 #3731

Im on the side of the dev taking his tiime in completeing this
However I think the dev should consider creating interim coins just as NEM did, this way he wouldnt feel rushed and people can do as they please with their stake and give others an opportunity to join

TwinWinNerD
Legendary
*
Offline Offline

Activity: 1680
Merit: 1001


CEO Bitpanda.com


View Profile WWW
June 15, 2014, 06:55:15 PM
 #3732

Im on the side of the dev taking his tiime in completeing this
However I think the dev should consider creating interim coins just as NEM did, this way he wouldnt feel rushed and people can do as they please with their stake and give others an opportunity to join

I already offered my  service as escrow for the launch on NXT AE, but this would only make sense, when the launch is weeks away. Otherwise it is too much hassle!

BitzMD
Sr. Member
****
Offline Offline

Activity: 418
Merit: 250



View Profile
June 15, 2014, 07:00:40 PM
 #3733

Im on the side of the dev taking his tiime in completeing this
However I think the dev should consider creating interim coins just as NEM did, this way he wouldnt feel rushed and people can do as they please with their stake and give others an opportunity to join

I already offered my  service as escrow for the launch on NXT AE, but this would only make sense, when the launch is weeks away. Otherwise it is too much hassle!

I still think it not a bad idea to release interm coins, review the code, let the community test and report bugs and then release the real deal. That should be ~2 weeks.

cawson
Full Member
***
Offline Offline

Activity: 196
Merit: 100


View Profile
June 15, 2014, 11:09:17 PM
 #3734

v0.61 is ok?  Huh
eXo_coin
Sr. Member
****
Offline Offline

Activity: 294
Merit: 250


View Profile WWW
June 15, 2014, 11:16:21 PM
 #3735

Yes, as promised, we will release huge parts of the code prior to the launch. Since that will be ~12,000 lines (I would need to check that first to be sure but that's close to reality I guess) the community surely will need some time to check.





When I go to the Settings tab and click Save in the "Change local addresses states", 0.1 EXO always gets deducted from my wallet balance. Is there a fee for changing states?
Yes, an address change will initiate a special transaction. It will be treated like a "real" transaction and therefore will cause a fee to be applied (it will appear in the transaction history in the block explorer as well). In 0.60.1 you will get a notification before a fee will be charged anywhere in the program.

Also in the Settings tab, if the wallet in not in the decrypted state and I click the Save button, it will ask for the passphrase. If I leave the field blank and submit it, a message box pops up with "An internal error has occurred: unknown cause" instead of the "Your passphrase is not valid." message.
Thanks for reporting! Fixed.



tried to send 999.99 but the client sends 1000.88
                   888.998                              889.88
                   888.889                               888.7    
                   111.991                                112.81
                      11.9                                     11.9 ---- this is ok
                       11.199                                 11.199 --- this is ok
                       11.99                                   12.8
                        88.98                                  89.78
                        11.91                                  12
                         11.92                                 12.1
                         11.93                                 12.2
                          11.933                               12.23
                          11.934                               12.234
Confirmed, the first few give the same result here

Had a similar thing with
1.001                 1.1
1.01                  1.1

found the cause. Thanks again for reporting and investigation! Fixed (but needs testing).


Hi dev.
Check peerlist, says:
>>try to connect to 192.3.134.164:60702:0
>>try to connect to 192.3.52.31:60702:0
>>try to connect to 192.227.237.33:60702:0
>>try to connect to 192.210.213.51:60702:0
>>try to connect to 192.3.52.43:60702:0
>>try to connect to 192.227.176.87:60702:0
>>try to connect to 27.11.15.214:60702:0
>>try to connect to 118.92.250.2:60702:0
>>try to connect to 116.225.74.44:60702:0
>>try to connect to 129.187.45.145:60701:0
>>try to connect to 178.124.205.127:32960:0
>>try to connect to 24.63.197.238:60702:0
>>try to connect to 186.88.165.76:60702:0
>>try to connect to 83.128.194.221:54648:0
>>try to connect to 58.8.233.168:60702:0
>>try to connect to 27.11.15.214:2786:0
>>try to connect to 27.11.15.214:2791:0
>>try to connect to 27.11.15.214:2810:0
>>try to connect to 27.11.15.214:2812:0
>>try to connect to 78.62.219.252:60702:0

I saw that has several different ports. Does not have old clients in that list?
Theoretically would add anyone by add peer command.
Is there a validation between them to see if they are the correct version?
Different ports are normal. If you are behind a NAT router, proxy, whatelse you most likely have a different port to the extranet than within the intranet. That is no problem.

Although all peers will be added to that list regarding of version information the client will only finish the handshake with peers of allowed versions. At the moment that is only 0.6 (at a later time it may be ok to accept older versions).


I have the same problem getting stuck on block 57 and/or 88

Deleting the blocks and restarting doesn't really help.

Then I noticed this on the debug console :

Code:
>get version

current version (locally): V0.60.0
latest version (network): V0.59.1

I tried blocking some peers with the command disable peer IP:PORT but that doesn't seem to work.
Since many of you have issues with syncing up larger blocks we will adjust the sendReliable parameters to try harder to get the parts of the blocks before giving up. "theoretically fixed".

I do not know if it helps. I left my client running since yesterday in the amazon server and seemed fine. Arrived at block 87.
Now i deleted the blocks, rebooted dai gave the problem mentioned.
My log:
https://mega.co.nz/#!W4JX3TAT!7jwiBJYdwH3EN-vbJZdLjYiBD7Zh57p-d9U3YA9Umg4
Checked your log file, thanks for uploading. That log looks good. In line 98,957 it states "new block started with id=98" therafter you initiated successfully a transaction and closed the program properly.




Once the major chain async bug is fixed we will release a 0.60.1 version.





We just started an issue tracking project here: https://sourceforge.net/p/exocoin/tickets/


That way we can more clearly communicate what we are working on, what already has been reported, what the current state of specific issues is and it helps to identify the issues if it is a longterm problem (like the chain async problem. We can now easier refer to a ticket id and everyone knows about what we are talking etc).

That idea came from a forum member (I dont want to name him if he would not want it - you never know) - thank you!
That clearly helps a lot in communication between community<->exocoin team


We got many improvement suggestions and bug reports (thanks!!). Some of them already are in the new ticket system and some are not (yet). Please wait some more days to fetch up with everything.

Also, we did not get that much votes yet on our logo thread: https://bitcointalk.org/index.php?topic=574490.0
please check out if not already done. Also note, that there is a 2nd independend vote on our website where you can vote as well if you already have an exocoin.org account.



More about the current status, especially regarding the chain async issue soon.


best regards
eXocoin

flankliu
Sr. Member
****
Offline Offline

Activity: 335
Merit: 250


View Profile
June 15, 2014, 11:32:42 PM
 #3736

Yes, as promised, we will release huge parts of the code prior to the launch. Since that will be ~12,000 lines (I would need to check that first to be sure but that's close to reality I guess) the community surely will need some time to check.





When I go to the Settings tab and click Save in the "Change local addresses states", 0.1 EXO always gets deducted from my wallet balance. Is there a fee for changing states?
Yes, an address change will initiate a special transaction. It will be treated like a "real" transaction and therefore will cause a fee to be applied (it will appear in the transaction history in the block explorer as well). In 0.60.1 you will get a notification before a fee will be charged anywhere in the program.

Also in the Settings tab, if the wallet in not in the decrypted state and I click the Save button, it will ask for the passphrase. If I leave the field blank and submit it, a message box pops up with "An internal error has occurred: unknown cause" instead of the "Your passphrase is not valid." message.
Thanks for reporting! Fixed.



tried to send 999.99 but the client sends 1000.88
                   888.998                              889.88
                   888.889                               888.7    
                   111.991                                112.81
                      11.9                                     11.9 ---- this is ok
                       11.199                                 11.199 --- this is ok
                       11.99                                   12.8
                        88.98                                  89.78
                        11.91                                  12
                         11.92                                 12.1
                         11.93                                 12.2
                          11.933                               12.23
                          11.934                               12.234
Confirmed, the first few give the same result here

Had a similar thing with
1.001                 1.1
1.01                  1.1

found the cause. Thanks again for reporting and investigation! Fixed (but needs testing).


Hi dev.
Check peerlist, says:
>>try to connect to 192.3.134.164:60702:0
>>try to connect to 192.3.52.31:60702:0
>>try to connect to 192.227.237.33:60702:0
>>try to connect to 192.210.213.51:60702:0
>>try to connect to 192.3.52.43:60702:0
>>try to connect to 192.227.176.87:60702:0
>>try to connect to 27.11.15.214:60702:0
>>try to connect to 118.92.250.2:60702:0
>>try to connect to 116.225.74.44:60702:0
>>try to connect to 129.187.45.145:60701:0
>>try to connect to 178.124.205.127:32960:0
>>try to connect to 24.63.197.238:60702:0
>>try to connect to 186.88.165.76:60702:0
>>try to connect to 83.128.194.221:54648:0
>>try to connect to 58.8.233.168:60702:0
>>try to connect to 27.11.15.214:2786:0
>>try to connect to 27.11.15.214:2791:0
>>try to connect to 27.11.15.214:2810:0
>>try to connect to 27.11.15.214:2812:0
>>try to connect to 78.62.219.252:60702:0

I saw that has several different ports. Does not have old clients in that list?
Theoretically would add anyone by add peer command.
Is there a validation between them to see if they are the correct version?
Different ports are normal. If you are behind a NAT router, proxy, whatelse you most likely have a different port to the extranet than within the intranet. That is no problem.

Although all peers will be added to that list regarding of version information the client will only finish the handshake with peers of allowed versions. At the moment that is only 0.6 (at a later time it may be ok to accept older versions).


I have the same problem getting stuck on block 57 and/or 88

Deleting the blocks and restarting doesn't really help.

Then I noticed this on the debug console :

Code:
>get version

current version (locally): V0.60.0
latest version (network): V0.59.1

I tried blocking some peers with the command disable peer IP:PORT but that doesn't seem to work.
Since many of you have issues with syncing up larger blocks we will adjust the sendReliable parameters to try harder to get the parts of the blocks before giving up. "theoretically fixed".

I do not know if it helps. I left my client running since yesterday in the amazon server and seemed fine. Arrived at block 87.
Now i deleted the blocks, rebooted dai gave the problem mentioned.
My log:
https://mega.co.nz/#!W4JX3TAT!7jwiBJYdwH3EN-vbJZdLjYiBD7Zh57p-d9U3YA9Umg4
Checked your log file, thanks for uploading. That log looks good. In line 98,957 it states "new block started with id=98" therafter you initiated successfully a transaction and closed the program properly.




Once the major chain async bug is fixed we will release a 0.60.1 version.





We just started an issue tracking project here: https://sourceforge.net/p/exocoin/tickets/


That way we can more clearly communicate what we are working on, what already has been reported, what the current state of specific issues is and it helps to identify the issues if it is a longterm problem (like the chain async problem. We can now easier refer to a ticket id and everyone knows about what we are talking etc).

That idea came from a forum member (I dont want to name him if he would not want it - you never know) - thank you!
That clearly helps a lot in communication between community<->exocoin team


We got many improvement suggestions and bug reports (thanks!!). Some of them already are in the new ticket system and some are not (yet). Please wait some more days to fetch up with everything.

Also, we did not get that much votes yet on our logo thread: https://bitcointalk.org/index.php?topic=574490.0
please check out if not already done. Also note, that there is a 2nd independend vote on our website where you can vote as well if you already have an exocoin.org account.



More about the current status, especially regarding the chain async issue soon.


best regards
eXocoin
great job,thanks dev.

rramires
Full Member
***
Offline Offline

Activity: 231
Merit: 100



View Profile
June 15, 2014, 11:36:58 PM
 #3737

Yes, as promised, we will release huge parts of the code prior to the launch. Since that will be ~12,000 lines (I would need to check that first to be sure but that's close to reality I guess) the community surely will need some time to check.





When I go to the Settings tab and click Save in the "Change local addresses states", 0.1 EXO always gets deducted from my wallet balance. Is there a fee for changing states?
Yes, an address change will initiate a special transaction. It will be treated like a "real" transaction and therefore will cause a fee to be applied (it will appear in the transaction history in the block explorer as well). In 0.60.1 you will get a notification before a fee will be charged anywhere in the program.

Also in the Settings tab, if the wallet in not in the decrypted state and I click the Save button, it will ask for the passphrase. If I leave the field blank and submit it, a message box pops up with "An internal error has occurred: unknown cause" instead of the "Your passphrase is not valid." message.
Thanks for reporting! Fixed.



tried to send 999.99 but the client sends 1000.88
                   888.998                              889.88
                   888.889                               888.7    
                   111.991                                112.81
                      11.9                                     11.9 ---- this is ok
                       11.199                                 11.199 --- this is ok
                       11.99                                   12.8
                        88.98                                  89.78
                        11.91                                  12
                         11.92                                 12.1
                         11.93                                 12.2
                          11.933                               12.23
                          11.934                               12.234
Confirmed, the first few give the same result here

Had a similar thing with
1.001                 1.1
1.01                  1.1

found the cause. Thanks again for reporting and investigation! Fixed (but needs testing).


Hi dev.
Check peerlist, says:
>>try to connect to 192.3.134.164:60702:0
>>try to connect to 192.3.52.31:60702:0
>>try to connect to 192.227.237.33:60702:0
>>try to connect to 192.210.213.51:60702:0
>>try to connect to 192.3.52.43:60702:0
>>try to connect to 192.227.176.87:60702:0
>>try to connect to 27.11.15.214:60702:0
>>try to connect to 118.92.250.2:60702:0
>>try to connect to 116.225.74.44:60702:0
>>try to connect to 129.187.45.145:60701:0
>>try to connect to 178.124.205.127:32960:0
>>try to connect to 24.63.197.238:60702:0
>>try to connect to 186.88.165.76:60702:0
>>try to connect to 83.128.194.221:54648:0
>>try to connect to 58.8.233.168:60702:0
>>try to connect to 27.11.15.214:2786:0
>>try to connect to 27.11.15.214:2791:0
>>try to connect to 27.11.15.214:2810:0
>>try to connect to 27.11.15.214:2812:0
>>try to connect to 78.62.219.252:60702:0

I saw that has several different ports. Does not have old clients in that list?
Theoretically would add anyone by add peer command.
Is there a validation between them to see if they are the correct version?
Different ports are normal. If you are behind a NAT router, proxy, whatelse you most likely have a different port to the extranet than within the intranet. That is no problem.

Although all peers will be added to that list regarding of version information the client will only finish the handshake with peers of allowed versions. At the moment that is only 0.6 (at a later time it may be ok to accept older versions).


I have the same problem getting stuck on block 57 and/or 88

Deleting the blocks and restarting doesn't really help.

Then I noticed this on the debug console :

Code:
>get version

current version (locally): V0.60.0
latest version (network): V0.59.1

I tried blocking some peers with the command disable peer IP:PORT but that doesn't seem to work.
Since many of you have issues with syncing up larger blocks we will adjust the sendReliable parameters to try harder to get the parts of the blocks before giving up. "theoretically fixed".

I do not know if it helps. I left my client running since yesterday in the amazon server and seemed fine. Arrived at block 87.
Now i deleted the blocks, rebooted dai gave the problem mentioned.
My log:
https://mega.co.nz/#!W4JX3TAT!7jwiBJYdwH3EN-vbJZdLjYiBD7Zh57p-d9U3YA9Umg4
Checked your log file, thanks for uploading. That log looks good. In line 98,957 it states "new block started with id=98" therafter you initiated successfully a transaction and closed the program properly.




Once the major chain async bug is fixed we will release a 0.60.1 version.





We just started an issue tracking project here: https://sourceforge.net/p/exocoin/tickets/


That way we can more clearly communicate what we are working on, what already has been reported, what the current state of specific issues is and it helps to identify the issues if it is a longterm problem (like the chain async problem. We can now easier refer to a ticket id and everyone knows about what we are talking etc).

That idea came from a forum member (I dont want to name him if he would not want it - you never know) - thank you!
That clearly helps a lot in communication between community<->exocoin team


We got many improvement suggestions and bug reports (thanks!!). Some of them already are in the new ticket system and some are not (yet). Please wait some more days to fetch up with everything.

Also, we did not get that much votes yet on our logo thread: https://bitcointalk.org/index.php?topic=574490.0
please check out if not already done. Also note, that there is a 2nd independend vote on our website where you can vote as well if you already have an exocoin.org account.



More about the current status, especially regarding the chain async issue soon.


best regards
eXocoin

OK, thanks for the information.

Tickets on sourceforge, will help track and contain anxiety.
We can follow the progress there.

A curiosity, "exocoin.db" is encrypted? I tried to open to see.
eXo_coin
Sr. Member
****
Offline Offline

Activity: 294
Merit: 250


View Profile WWW
June 16, 2014, 12:55:53 AM
 #3738

A curiosity, "exocoin.db" is encrypted? I tried to open to see.
No it is not. However, as I tried now for my self I cannot access it with an external program as well. But the program can read and write to it without problems. Seems to be the file format. It states "CSqlite format 3" rather than "Sqlite format 3" (did not know that there is a different format if created by c++ ??). But I do not know if that is really the problem. You can view the content as raw file with notepad to get a general idea at least. Maybe someone else can enlight this a bit more.

hala
Hero Member
*****
Offline Offline

Activity: 546
Merit: 500


View Profile
June 16, 2014, 12:58:44 AM
 #3739

 

 take you time , just make everything fine .  Wink

 
hala
Hero Member
*****
Offline Offline

Activity: 546
Merit: 500


View Profile
June 16, 2014, 01:06:53 AM
 #3740




We just started an issue tracking project here: https://sourceforge.net/p/exocoin/tickets/




 the bug system is wonderful , can anyone has the right to report bug into it ?

#edit :

 Ticket creations can only be done by admin as for now.
 We currently fetch up all your (bug) reports and will add them soon.
Pages: « 1 ... 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175 176 177 178 179 180 181 182 183 184 185 186 [187] 188 189 190 191 192 193 194 195 196 197 198 199 200 201 202 203 204 205 206 207 208 209 210 211 212 213 214 215 216 217 218 219 220 221 222 223 224 225 226 227 228 229 230 231 232 233 234 235 236 237 ... 307 »
  Print  
 
Jump to:  

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!