# Duniter-squid version 0.2.8
**URL:** https://forum.duniter.org/t/duniter-squid-version-0-2-8/12690
**Category:** Indexers
**Created:** [13 November 2024 14:42 UTC](https://forum.duniter.org/t/duniter-squid-version-0-2-8/12690 "2024-11-13T14:42:16Z")
**Posts on this page:** 8
**Page:** 1
### Author:  [@HugoTrentesaux](https://forum.duniter.org/u/HugoTrentesaux)
#### Post date: [13 November 2024 14:42 UTC](https://forum.duniter.org/t/duniter-squid-version-0-2-8/12690/1 "2024-11-13T14:42:16Z")
Duniter squid version 0.2.8 is out. It’s adding the information of the account creation block as suggested in [Ğ1nkgo v2 support progress, plan and pubkeys/address proposal](https://forum.duniter.org/t/g1nkgo-v2-support-progress-plan-and-pubkeys-address-proposal/12617). This will in particular allow to know if the account existed in v1 (and so b58 pubkey could be displayed to the user to avoid address change) or was created in v2.
The `expireOn` field of identities has been fixed, [see the schema](https://git.duniter.org/nodes/duniter-squid/-/blob/main/schema.graphql?ref_type=heads#L229-236) for more info about its meaning.
One of my indexers is up to date, the other is indexing.
[edit] the 0.2.9 is being checked with a fix on genesis cert `updatedOn` field and the pre-genesis `expireOn` estimations
---
### Author:  [@vjrj](https://forum.duniter.org/u/vjrj)
#### Post date: [24 November 2024 10:16 UTC](https://forum.duniter.org/t/duniter-squid-version-0-2-8/12690/2 "2024-11-24T10:16:31Z")
Thanks indeed @HugoTrentesaux.
I will be great if we can query the current version of the schema using by a node, in order to detect which nodes are up-to-date and which are not. I don’t know if this can be done already.
Better if this version uses [https://semver.org/](https://semver.org/) so we can compare programmaticly better.
This is needed in order to adapt our clients code to future schema changes properly and prevent runtime errors.
---
### Author:  [@vjrj](https://forum.duniter.org/u/vjrj)
#### Post date: [25 November 2024 04:42 UTC](https://forum.duniter.org/t/duniter-squid-version-0-2-8/12690/3 "2024-11-25T04:42:06Z")
For instance I still get different schemas as [I mentioned here](https://forum.duniter.org/t/duniter-squid-doubts/12563/8).
```auto
$ npx get-graphql-schema https://gdev-indexer.p2p.legal/v1/graphql > /tmp/sc1
$ npx get-graphql-schema https://squid.gdev.coinduf.eu/v1/graphql > /tmp/sc2
$ view -d /tmp/sc1 /tmp/sc2
```
cc @poka
---
### Author:  [@poka](https://forum.duniter.org/u/poka)
#### Post date: [25 November 2024 06:36 UTC](https://forum.duniter.org/t/duniter-squid-version-0-2-8/12690/4 "2024-11-25T06:36:56Z")
I probably should stop this one, please start one.
---
### Author:  [@vjrj](https://forum.duniter.org/u/vjrj)
#### Post date: [25 November 2024 07:56 UTC](https://forum.duniter.org/t/duniter-squid-version-0-2-8/12690/5 "2024-11-25T07:56:48Z")
I’ll already have one. The thing is [how to know the schema version](https://forum.duniter.org/t/duniter-squid-version-0-2-8/12690/2) of each node.
---
### Author:  [@HugoTrentesaux](https://forum.duniter.org/u/HugoTrentesaux)
#### Post date: [25 November 2024 11:11 UTC](https://forum.duniter.org/t/duniter-squid-version-0-2-8/12690/6 "2024-11-25T11:11:23Z")
> [@vjrj](#):
>
> I will be great if we can query the current version of the schema using by a node, in order to detect which nodes are up-to-date and which are not.
I agree. [#40](https://git.duniter.org/nodes/duniter-squid/-/issues/40) aims to expose the version of the indexer through the API. For the moment, there were very frequent breaking changes, so I just kept incrementing minor version number, but we should soon move to a cleaner version numbering scheme. I did not make the effort to do it properly because of the lack of response to indexer updates, but if I see more people installing indexers, I’ll put more effort in it.
---
### Author:  [@vjrj](https://forum.duniter.org/u/vjrj)
#### Post date: [1 December 2024 09:07 UTC](https://forum.duniter.org/t/duniter-squid-version-0-2-8/12690/7 "2024-12-01T09:07:18Z")
Hi again @HugoTrentesaux.
I’m trying to play with this to later implement it in the client. I think you added `identity.createdOn`. Then, if I do a query:
```auto
query GetNewAccounts {
account(where: { identity: { createdOn: { _neq: 0 } } }) {
id
isActive
identity {
id
isMember
name
accountId
status
createdOn
account {
isActive
}
index
}
}
}
```
I only find in our test environment 5 accounts with identities that I will show with the new addressing.
What about accounts without identity?
For instance, my old v1 account (migrated by Gecko):
```auto
query GetSomeAccount {
account(where: { id: { _eq: "5DpRqhjEof2WMFoAYTAqqoQzyBH9zRRmAbBZGQm9uZSzNeY6" } }) {
id
isActive
identity {
id
isMember
name
accountId
status
createdOn
account {
isActive
}
index
}
}
}
```
Returns:
```auto
{
"data": {
"account": [
{
"id": "5DpRqhjEof2WMFoAYTAqqoQzyBH9zRRmAbBZGQm9uZSzNeY6",
"isActive": true,
"identity": null
}
]
}
}
```
In other words, I missing a way to know if a simple wallet/account was created in v1 or not.
---
### Author:  [@HugoTrentesaux](https://forum.duniter.org/u/HugoTrentesaux)
#### Post date: [1 December 2024 16:09 UTC](https://forum.duniter.org/t/duniter-squid-version-0-2-8/12690/8 "2024-12-01T16:09:05Z")
> [@vjrj](#):
>
> I think you added `identity.createdOn`.
This one was already there. The one I added is `account.createdOn`:
The corresponding query is:
```auto
query GetNewAccounts {
account(limit: 10, where: {createdOn: {_gt: 0}}) {
id
identity { name }
}
}
{
"data": {
"account": [
{
"id": "5E6q47RRGZU15LjUiBTm2DZjpqFKAjRNafYS8YV8AzTQZtLG",
"identity": {
"name": "cgeek"
}
},
{
"id": "5Dq8xjvkmbz7q4g2LbZgyExD26VSCutfEc6n4W4AfQeVHZqz",
"identity": {
"name": "HugoTrentesaux"
}
},
{
"id": "5HDikVWZ2xHfqvVVFwex5zmRsH4LuR3KqMgKZYEbCSjStSKw",
"identity": {
"name": "moul"
}
},
{
"id": "5CQ8T4qpbYJq7uVsxGPQ5q2df7x3Wa4aRY6HUWMBYjfLZhnn",
"identity": {
"name": "poka"
}
},
{
"id": "5F6xAX1k6eRKUGrF7exifKcS2K2SB781Cn6soV1kahjwkGpg",
"identity": {
"name": "14572"
}
},
{
"id": "5CfodrEFe64MJtWvfhTHYBuUySr4WXLv2B41mZFucTXSGMFA",
"identity": null
},
{
"id": "5Cw6cF46Et7hpGXAnYD1XeEMQrfuPioMq4nyrVpUzcHvi575",
"identity": null
},
{
"id": "5GBVhdJUdsGhxozu6R8X6x2pTZvuuW46s7JSU4tiW7Zd3WmY",
"identity": {
"name": "Pini"
}
},
{
"id": "5Epo9NJL5TpEWBhDobZoWK8yezCYnDg9dTXMB486LhdzWz85",
"identity": null
},
{
"id": "5CJKhFCpdSpumgWjSZ3TQmejJuHV6iELJrtdrfs38SXuiQeB",
"identity": null
}
]
}
}
```
As you can see, some accounts have associated identities, some don’t (null).
Thanks for your question 🙂
This helps me clarify the schema available here: [schema.graphql · main · nodes / duniter-squid · GitLab](https://git.duniter.org/nodes/duniter-squid/-/blob/main/schema.graphql?ref_type=heads#L119). I will add more documentation in it.